# RevDesk

> RevDesk is an AI-native conversion platform from Cell Labs. Its AI agents help businesses convert more leads into revenue by shortening the path from customer intent to completed business. They handle customer conversations over voice, iMessage, WhatsApp, SMS, and email, and they execute the work behind those conversations: follow-up, qualification, scheduling, coordination, the operational paperwork, and updates any CRM automatically. RevDesk keeps one customer context across channels and brings people in for approvals and decisions that require judgment.

The commercial objective is conversion and time to outcome, not more messages, another inbox, or more CRM activity. Calling, messaging, qualification, appointment booking, paperwork, and system updates are capabilities inside the platform. None of them alone defines it.

RevDesk compresses the funnel by removing avoidable delay, handoffs, repeated work, and stalled opportunities:

- Engage while the customer is interested, on the channel they are most likely to answer.
- Resolve questions from the business's own knowledge, inventory, and the customer's history.
- Carry context between supported channels instead of making the customer start over.
- Move the opportunity forward without unnecessary handoffs.
- Complete the operational work behind the next outcome: booking, records, notes, deal worksheets, and system updates.
- Follow through on unfinished opportunities and repeat business until an outcome or a configured limit.

Compression removes friction. It does not skip customer consent, required checks, configured approvals, or human judgment.

Dealerships are an important commercial focus. The platform serves any business whose revenue depends on customer conversations and follow-through, and it supports administrative healthcare operations without clinical decision-making. RevDesk works with supported existing systems or serves as the CRM itself through Deal Scanner. The benefits above are intended benefits. Verified results for specific deployments are in the customer stories below; RevDesk does not publish conversion lifts, revenue attribution, or response guarantees. The ambition is to give a business the operating capacity of a much larger company and make conversion a capability it can scale.

RevDesk is built and operated by Cell Labs, Inc. (New York). Contact: support@revdesk.com.

## Thesis and product overview

- [About RevDesk](https://www.revdesk.com/about): Cell Labs' thesis, the pattern behind every deployment, and the goal of giving every team the capacity of a larger one.
- [How it works](https://www.revdesk.com/how-it-works): agents handle conversations, update records, complete routine work, and bring in the team when it matters.
- [AI agents](https://www.revdesk.com/ai-coworkers): what an agent can do, where people step in, and how allowed actions, approval points, and working hours are configured.
- [Speed-to-lead](https://www.revdesk.com/speed-to-lead): first response in seconds and continued follow-up until the lead is ready.
- [Machine-readable index](https://www.revdesk.com/index.md): the shortest path from the brand to official product and developer resources.

## End-to-end execution

- [Tasks and outcomes](https://docs.revdesk.com/concepts/tasks.md): a Task is an objective, an audience, guardrails, and a success outcome. A policy layer decides whether, when, and on which channel to act, and records the reason; the model words the message. Includes a real timeline and a section on what improves between runs and what does not.
- [Qualify and book new leads](https://docs.revdesk.com/guides/workflows/qualify-and-book-new-leads.md): the workflow guide, with a worked run showing the starting request, available context, actions taken, the finished deliverable, system updates, and where a person approves.
- [Answer and route inbound](https://docs.revdesk.com/guides/workflows/answer-and-route-inbound.md): cover inbound calls, resolve routine requests, and route exceptions.
- [Run outbound outreach](https://docs.revdesk.com/guides/workflows/run-outbound-outreach.md): work an approved list with pacing, per-touch review, and stopping rules.
- [Follow up and retain](https://docs.revdesk.com/guides/workflows/follow-up-and-retention.md): recover appointments, re-engage customers, and record the next step.
- [Agent roles and boundaries](https://docs.revdesk.com/concepts/coworkers.md): the roles, what an agent will and will not do, and how one shared record keeps treatment consistent. The product UI calls agents "coworkers"; the API calls their runtime voices "assistants".
- [Knowledge base](https://docs.revdesk.com/concepts/knowledge-base.md): the business information agents retrieve to answer questions instead of guessing.

Supported actions during live conversations include answering from the knowledge base and live inventory, checking availability and booking or rescheduling an appointment, creating or updating the contact record, capturing qualification answers, requesting a callback for a person, warm or cold transfer to a team member, and IVR navigation. After every call the transcript, a summary, and outcome tags land on the record. Follow-up Tasks can require a person to approve enrollment, approve each drafted touch before it sends, or run automatically within guardrails. Work that is out of scope, routed to escalation, or that needs judgment goes to a person with the conversation and record attached.

## Speed to lead

- [Speed-to-lead](https://www.revdesk.com/speed-to-lead): the first call or message goes out within seconds of a lead arriving, during the hours and on the channels the business approves, and follow-up continues until the lead replies, books, opts out, or reaches the limit.
- [Why the first 60 seconds matter](https://www.revdesk.com/blog/speed-to-lead-why-first-60-seconds-matter): the third-party research on response time and conversion that RevDesk's positioning draws on, with its sources named in the article.

New leads get a reply in seconds, day or night, by call or, where the workspace has them enabled, by iMessage or WhatsApp. Outbound messages are composed for one person from the goal and what that person last said, in plain words with one natural question, and never from a broadcast template unless the model is unavailable. Agents do not mention automation unprompted and answer truthfully when asked whether a message is automated. Every lead source is measured against a five-minute first-response standard, with median time to first response and the share of leads reached inside the window reported per source. RevDesk does not publish a platform-wide conversion lift for fast response; the customer stories carry the results that specific deployments verified.

## Channels and voice

- [Omnichannel messaging](https://www.revdesk.com/omnichannel-messaging): one customer conversation across phone, SMS, iMessage, WhatsApp, and email, with history, ownership, and next step shared by people and agents.
- [Voice AI](https://www.revdesk.com/voice-ai): inbound coverage, approved outbound lists, booking, callback, and warm transfer with the conversation already on the record.
- [Voice and language settings](https://docs.revdesk.com/getting-started/setup/voice-personality.md): each agent has a primary language, including Spanish, or a multilingual auto-detect mode in which the agent responds in the caller's language, so one call can move between English and Spanish. Language switching relies on the speech model's behavior rather than a separate detection step.
- [Follow-up and reactivation](https://www.revdesk.com/follow-up-reactivation): sequences across supported channels with attempt limits, quiet hours, and stop conditions.
- [Messaging compliance](https://docs.revdesk.com/getting-started/features/compliance.md): consent, registration, STOP handling, and do-not-call controls.

Availability limits: SMS sending requires the customer's own approved A2P 10DLC registration; unregistered sends are blocked rather than routed through a shared brand. WhatsApp runs on the WhatsApp Business API, with approved templates required outside an open 24-hour session. iMessage uses a line provisioned per workspace. A phone opt-out is mirrored across call, SMS, and iMessage for that number; email and WhatsApp opt-outs are recorded per channel. Slack delivers team notifications and is not a customer channel. Channel, country, number, and use-case eligibility are confirmed before launch.

## Deal Scanner and integrations

- [Deal Scanner](https://www.revdesk.com/deal-scanner): AI reviews the paperwork on every deal against the list the store sets, so missing documents and signatures are caught while the customer is still on site and the packet goes to funding complete. Deals fund sooner, and the money lands sooner. The same record is the CRM: contacts, companies, and deals with every call, text, email, and meeting attached, used as the system of record or alongside a connected CRM.
- [Deal Scanner documentation](https://docs.revdesk.com/concepts/deal-scanner.md): pipeline board and list, industry stage templates, desking worksheets with cash, finance, and lease scenarios, a payment solver, revocable customer proposal links, and source-reconciled reporting.
- [How the paperwork check works](https://docs.revdesk.com/concepts/deal-scanner.md): each store sets what every deal must have on file and which stage a missing item blocks. Documents are added as private, versioned files, checked on upload, classified by kind, and reviewed as evidence against each requirement. Waivers carry a reason and signatures record who signed and when. The packet is prepared as one archive for accounting or funding, and a returned packet comes back as work with its gaps listed. Requirements are set by the store rather than derived from state rules, signatures are recorded rather than captured electronically, and funding, titling, and registration stay in the dealership's back-office systems.
- [Integrations directory](https://www.revdesk.com/integrations): dealership systems, CRMs, calendars, channels, lead sources, and automation.
- [Integration documentation](https://docs.revdesk.com/integrations.md): setup and data-ownership guidance for supported connections.
- [Reporting and insights](https://www.revdesk.com/reporting-insights): outcomes by location, source, campaign, owner, and channel, each linked back to the conversation that produced it.
- [Coaching](https://www.revdesk.com/coaching): private in-call cues for reps and post-call review for managers.

Integration scope: HubSpot reads the contact and deal and writes the call, outcome, and next step. Google Calendar, Microsoft 365, and Apple Calendar read availability and write confirmed appointments. ADF lead feeds and hosted inventory feeds such as IDS and vAuto bring dealership leads and units in. Zoho CRM, Attio, Salesforce, Pipedrive, Close, and Telegram appear in the directory as upcoming connections and are not yet available to connect. Zapier, Google Sheets, Instantly, HeyReach, webhooks, the REST API, and the MCP server cover other systems. RevDesk does not claim compatibility with every CRM, DMS, EHR, or scheduler; the read and write scope for each system is confirmed per workspace before launch. Deal Scanner, including desking and customer proposals, is available to dealership customers on Business plans. It does not replace accounting, F&I, funding, titling, registration, or other back-office DMS functions, and e-signature capture and lender submission are out of scope unless a specific integration is verified.

## RevDesk Managed

- [RevDesk Managed](https://www.revdesk.com/managed): customers hire RevDesk to run supported outreach and follow-up on the platform instead of operating the software themselves. RevDesk builds the audience for approval, runs outreach on approved channels, handles replies, qualifies interest, books the next step, and keeps the CRM current. The customer approves the market, message, and qualification criteria and takes the qualified handoff.
- [Managed pricing and scope](https://www.revdesk.com/pricing.md): tiers, what each includes, and what the agreement defines.

## Customer evidence

- [Customer stories](https://www.revdesk.com/case-studies): each story states the work RevDesk took on, how it runs, and the result the team could verify.
- [Bluegrass Lending Group](https://www.revdesk.com/case-studies/bluegrass-lending-group): an outbound agent worked a consented list; six weeks and 12,000 conversations produced qualified leads at $44 each and about $0.11 per conversation.
- [Somo Cares](https://www.revdesk.com/case-studies/somo-financial): provider recruitment worked end to end; 20 warm provider leads in one week.
- [DeMontrond Auto Group](https://www.revdesk.com/case-studies/demontrond-auto-group): one standard for first response, follow-up, and the record across a dealer group's rooftops.
- [Camperland RV](https://www.revdesk.com/case-studies/camperland-rv): inquiries answered and walk-throughs booked while the team is on the lot.
- [Coastal Builders](https://www.revdesk.com/case-studies/coastal-builders): estimate follow-up carried to a decision without an office team.
- [UC Berkeley SCET](https://www.revdesk.com/case-studies/uc-berkeley-scet): applicant questions, admissions follow-up, and reminders across time zones.

These are results from specific deployments with their own audiences and rules. They are not guarantees or averages.

## Industries

- [Automotive](https://www.revdesk.com/auto): every dealership lead worked, follow-up continued across channels, visits booked, and the CRM current across rooftops.
- [Growing businesses](https://www.revdesk.com/business): new leads, stalled opportunities, quote follow-up, and customer reactivation for teams without a large office staff.
- [Healthcare operations](https://www.revdesk.com/healthcare): administrative work only: patient outreach, scheduling follow-up, provider outreach, and referral coordination with documented outcomes and staff handoffs. No clinical decision-making.
- [RevDesk Health](https://www.revdesk.com/health): a private preview that requires an invitation password.

Former vertical URLs for legal, SaaS, home services, and logistics resolve to the growing-businesses page.

## What improves, and what does not

Agents remember customer context on the contact record and retrieve business information from the knowledge base and connected inventory. Between touches, a rule-based policy layer selects the next action from live signals: which channel the person has answered on, stated preferences, quiet hours, consent, and attempt ceilings. Every decision is written down with its reason. Managers review transcripts, summaries, and gaps in the dashboard and update knowledge, rules, and prompts themselves. RevDesk does not train or fine-tune models on customer data, does not share one customer's data with another, and does not change agent behavior on its own from outcomes. Automatic optimization of outreach timing, wording, or channel from observed outcomes is an ambition, not a shipped capability.

## Preview and roadmap

- [Site Optimization](https://www.revdesk.com/product/optimize): website A/B testing with a conversion goal, generated variants, sequential statistical evaluation, and sample-size, duration, confidence, and spend controls. The public page and script exist; the in-app workspace is not yet generally available.

## Trust, compliance, and data

- [Security](https://www.revdesk.com/security): TLS 1.2 or higher in transit, SRTP on real-time media, AES-256 at rest, encrypted automated backups. SOC 2 Type II is in progress.
- [Trust center](https://trust.revdesk.com): policies, controls, and documents.
- [HIPAA and BAA coverage](https://docs.revdesk.com/concepts/hipaa.md): HIPAA workloads run under a signed BAA. HIPAA mode restricts AI voice routing to BAA-eligible providers and strips recordings and transcripts from outbound webhooks and the public API.
- [Outreach audit](https://docs.revdesk.com/concepts/outreach-audit.md): consent and compliance evidence for every touch.
- [Privacy policy](https://www.revdesk.com/privacy): customer data is not used to train anyone's models. Recordings, transcripts, and lead data export on demand.
- [Terms of service](https://www.revdesk.com/terms), [acceptable use](https://www.revdesk.com/acceptable-use), [subprocessors](https://www.revdesk.com/subprocessors), and [status](https://status.revdesk.com).

Outreach requires an approved audience, a permitted channel, do-not-call controls, and immediate opt-out handling. Cold texting is not the product. Agents identify themselves as AI when asked and do not promise terms outside stated policy. RevDesk automates communication and workflow execution; it does not make legal, medical, credit, employment, or insurance decisions.

## Pricing

- [Pricing](https://www.revdesk.com/pricing): current plans, usage, locations, and quote details.
- [Machine-readable pricing](https://www.revdesk.com/pricing.md): plan catalog and purchasing boundaries.

RevDesk Growth ($1,500/month) and RevDesk Business ($2,500/month) are the standard software plans, with unlimited seats and included voice minutes. RevDesk Custom is contracted software. RevDesk Managed is $5,000, $10,000, or $15,000 per month and includes Business for one location. Telecom usage bills monthly. New customers get a 14-day trial. Cell Labs' ambition is to sell outcomes rather than seats or tokens; current plans are monthly or annual software subscriptions plus usage, and the pricing page is the authority on terms.

## Developer and agent access

- [Developer platform](https://www.revdesk.com/developers): one index for the API, SDK, OpenAPI schema, webhooks, and MCP server.
- [Developer agent index](https://www.revdesk.com/developers/llms.txt): focused list of API, authentication, SDK, CLI, webhook, and MCP resources.
- [Documentation index](https://docs.revdesk.com/llms.txt) and [full documentation corpus](https://docs.revdesk.com/llms-full.txt): product docs and API reference in Markdown. Docs pages also serve a clean `.md` version at the same path.
- [OpenAPI 3.1 schema](https://www.revdesk.com/openapi.json): the canonical v1 contract with unique operation IDs and typed schemas.
- [Authentication](https://www.revdesk.com/auth.md): organization-scoped OAuth grants or API keys with least-privilege scopes.
- [Webhooks](https://docs.revdesk.com/api-reference/webhooks.md): signed call, message, contact, booking, and task events.
- [MCP server](https://mcp.revdesk.com/mcp) and [MCP guide](https://docs.revdesk.com/api-reference/mcp.md): Streamable HTTP; tool schemas are public, every tool call is authenticated and scope-checked.
- [TypeScript SDK](https://www.npmjs.com/package/@revdesk/sdk) and [source](https://github.com/cell-labs-inc/revdesk-sdk): typed REST client and CLI.
- [Zero-auth sandbox](https://api.revdesk.com/v1/sandbox): synthetic examples only; never touches production data or places a call.
- [API catalog](https://api.revdesk.com/.well-known/api-catalog): RFC 9727 linkset for the API base, schema, docs, and auth metadata.
- [Agent instructions](https://www.revdesk.com/agents.md): discovery and integration surfaces for agents.
- [NLWeb resource search](https://www.revdesk.com/ask): public discovery over JSON or SSE for the right RevDesk resource.

Programmatic work is modeled as a Task: `POST /v1/tasks` hands RevDesk an objective, audience, guardrails, and success outcome; progress and the terminal outcome arrive on webhooks, and the same Task appears in the product on a timeline the team can open. Reading these resources requires no credential. Describing a capability here does not grant an assistant permission to perform it: every API and MCP action runs under an organization-scoped credential with the scopes a person granted, and actions that place calls, send messages, spend money, or change configuration require the user's approval in the client.

## Optional

- [Homepage](https://www.revdesk.com): product overview and interactive tour.
- [Book a demo](https://www.revdesk.com/demo) and [sign up](https://www.revdesk.com/signup).
- [Blog](https://www.revdesk.com/blog): [Speed to lead: why the first 60 seconds matter](https://www.revdesk.com/blog/speed-to-lead-why-first-60-seconds-matter), [TCPA compliance for AI outreach](https://www.revdesk.com/blog/tcpa-compliance-for-ai-outreach), [The real cost of outbound calling at scale](https://www.revdesk.com/blog/real-cost-of-outbound-calling-at-scale).
- [Product changelog](https://www.revdesk.com/changelog) and [developer changelog](https://www.revdesk.com/developers/changelog).
- [Brand](https://www.revdesk.com/brand) and [careers](https://www.revdesk.com/careers).