> ## Documentation Index > Fetch the complete documentation index at: https://docs.revdesk.com/llms.txt > Use this file to discover all available pages before exploring further. # Quickstart > Configure and test one complete RevDesk workflow before expanding the audience or channels. # Build one complete workflow Start with one trigger, one audience, one outcome, and one handoff path. The goal is to verify that work can enter RevDesk, reach the right person, produce a clear next step, and update the expected record. Exact setup screens depend on your plan, enabled channels, integrations, and deployment. Use [Launch your first workflow](/getting-started/onboarding) for the full checklist. ## 1. Create or join a workspace A workspace is the customer-facing name for your RevDesk organization. Add the business, locations, teammates, working hours, and the people responsible for handoffs. ## 2. Choose a narrow first outcome Good first outcomes are easy to recognize and verify: * Route an inbound call to the right person. * Respond to a new lead and book an appointment. * Re-engage an approved audience and hand off qualified interest. * Follow up after a visit and record the response. * Create or update the supported opportunity and next step. Avoid combining several audiences, departments, and outcomes in the first launch. ## 3. Connect the required systems and channels Connect only what the workflow needs. This may include: * A RevDesk or ported phone number * A supported messaging sender * Deal Operations or a verified CRM integration * A calendar used for availability and booking * A form, approved list, or integration that supplies eligible records Set up a number and review registration requirements. Review supported CRM, calendar, messaging, and automation connections. Evaluate one controlled workflow with test limits before production launch. Review the units, balances, and billing behavior that apply to your enabled channels. ## 4. Define the agent task Write down: * **Audience:** Which records are eligible and which must be excluded? * **Outcome:** What does completed work look like? * **Channels:** Which approved channels may the agent use? * **Schedule:** When may work run and how long may follow-up continue? * **Actions:** What may RevDesk say, create, update, book, or route? * **Approval:** Which actions require review? * **Handoff:** When should a person take over, and who owns the response? * **Stopping rules:** Which reply, outcome, opt-out, or exception ends the task? ## 5. Test from trigger to record update Use a test record and verify the whole path: 1. The record enters the correct workspace and location. 2. The agent receives the right context and starts within the configured schedule. 3. The opening conversation and reply handling match the approved playbook. 4. Booking, routing, approval, opt-out, and human handoff work as expected. 5. Deal Operations or the verified integration records the correct activity, owner, stage, appointment, outcome, and next step. 6. Managers can find the work and understand what needs attention. Launch to a controlled audience only after the complete path works. Expand one variable at a time, such as audience size, channel, location, or workflow. ## Next steps Verify customer, agent, teammate, and record behavior. Understand included voice minutes, native channel units, and the usage balance. Refine instructions after the base workflow is reliable. Build a custom integration or event consumer. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.