Skip to main content
A coworker is an AI teammate that owns one stage of your customer lifecycle. You hire one the way you would hire a person: pick the role, give it a name and a voice, answer a few questions about how you work, and it starts. Each one owns a stage. The Receptionist answers, Speed-to-Lead reaches new leads, Customer Care follows up after the job. They share one contact record and one calendar, so a lead that comes in on the phone and books by text is one conversation, not three.

The six roles

Every workspace starts with a Receptionist. It is the floor: it answers so nothing is missed. The other five are specialists you add as you need them. They group by what they do for you:
  • Core: Receptionist, Augmented Sales
  • Win new business: Speed-to-Lead, Outbound SDR
  • Keep and grow customers: Customer Care, Re-Engage
Packages pair the Receptionist with two specialists. See Pricing.

Templates

A template is a working coworker you can start from instead of a blank page. It carries a greeting, a conversation flow, the tools the coworker can call, and a sample of how it sounds on a real call. Browse them under Coworkers → Templates, filtered by industry and use case. Picking one seeds a new coworker with its greeting and flow already filled in. You can change anything afterwards.

Hiring one

1

Pick a role or a template

From Coworkers, choose a role card, or open Templates and pick a starting point.
2

Answer the setup questions

Each role asks what it needs to do the job. The Receptionist asks for your business hours and a transfer number. Speed-to-Lead asks where your leads come from. Outbound SDR asks you to attest that every contact has prior express written consent.
3

Choose a voice and personality

Pick the voice, the model tier, and the language. Write the greeting and the personality prompt, or keep the template’s.
4

Review and add

The coworker is created and its workflows are provisioned. It shows Setup needed until everything it depends on is connected, then flips to Active.

What you can change

The role itself is fixed once hired, because it is what the coworker is. To change the job, hire the coworker that does it.

Running more than one of a role

You can run several coworkers in the same role, for example two Augmented Sales coworkers covering different teams. One of them is the primary for that role, and it is the one that carries the subscription. Additional coworkers in a role you already hold do not add to your bill.

Firing one

Removing a coworker is scheduled, not immediate. It keeps working until the end of the billing period, and re-hiring it before then costs nothing. The Receptionist cannot be removed while you hold specialists, since it is what answers the phone.

One shared record

Your coworkers work from one contact record, and the data layer keeps it complete. Sourcing. Define your ICP (industry, size, geography, role, technology) and RevDesk produces a fresh batch of matching accounts and verified contacts on the cadence you pick. Net-new only. Existing CRM rows are excluded. See Source leads. Enrichment. Missing fields get filled, stale rows get refreshed, and unknown inbound callers get identified before a coworker picks up. Typical metric: enrichment hit rate ~85% on US business callers. See Enrich leads. Because the record is shared, a prospect gets one consistent treatment. The data layer enriches the record before anyone touches it. A coworker reaches out on the channel most likely to get an answer. If the prospect replies by text instead of picking up, the thread continues without re-asking what they already said. When intent crosses your threshold, the meeting lands on the right rep’s calendar with a structured note, a recording, and a transcript.

Boundaries

Coworkers operate inside well-defined limits.

Will do

Answer questions from your knowledge baseBook meetings against the right rep’s calendarQualify against your scoring criteriaTransfer to a human when intent spikes or the conversation calls for itFollow up by voice, SMS, email, or another call

Will not do

Speculate when the knowledge base doesn’t have the answerPromise terms outside your stated policiesClaim to be human when asked directlySurface or call data we do not have rights toHandle scenarios you’ve routed to escalation
When a conversation goes outside the knowledge base, the coworker captures contact details, hands off cleanly, and flags the gap in your dashboard so you can teach the team for next time.

Training the team

You teach your coworkers once, in one place. The same knowledge base, qualification rules, ICP definition, and brand voice apply to all of them.
1

Define your ICP and qualification criteria

Budget, timeline, fit, decision-maker, use case. Coworkers apply these in conversation and adapt to each caller rather than reading a rigid script.
2

Add your business knowledge

Pricing, product specs, common objections, policies, services. See Knowledge base.
3

Connect your CRM and calendar

Hand-off lands in HubSpot, LeadConnector, or Zoho with structured fields populated. Bookings land on the right rep’s calendar.
4

Review transcripts and iterate

Every conversation produces a transcript and a summary. Gaps surface in the dashboard, and you teach your coworkers from them.
Coworkers, agents, and assistants. The product calls them coworkers. The API does not.GET /v1/agents returns assistants, which are the runtime voices attached to your phone numbers and campaigns. They are not the same objects as the coworkers you hire on this page, and the counts will not match. A coworker provisions the workflows and assistants that do its work.There is no coworkers resource in the v1 API, and the scopes are agents:read and agents:write. When you are reading the API reference, read “agent” as “assistant”.

Jobs

Hand your coworkers an outcome and let them work every task until it happens.

Knowledge base

What your coworkers know about your business.

Voice and personality

Pick the voice and write the personality.

Pricing

Packages, and what each one includes.