Skip to main content
Most partners go from API key to live embed in under a day. The iframe setup is a single line of HTML. Lead import is a single API call.
No. Sub-accounts and embed tokens are managed entirely through your Partner API key. Your end users interact through the white-labeled embed — they never see Recover.
Yes. Every sub-account has independent prompt configuration, context files, sequences, and checklists. Changes to one account never affect another.
The AI flags the conversation for human handoff. Your users can see this in the embed dashboard and take over manually. You also receive a conversation.handoff_requested webhook.
Leads can text photos or PDFs directly. The AI downloads the file, matches it to the correct checklist item, and updates the checklist automatically. For data points (email, dates, etc.), the AI extracts them from the conversation.
Yes. All numbers are registered for the SMS use case. Opt-out keywords (STOP, UNSUBSCRIBE, etc.) are handled automatically. Messages respect quiet hours and rate limits.
Yes. Sequences and AI prompts can be configured for collections follow-up. The AI can be instructed to offer payment arrangements, send payment links, and escalate to human agents when needed.
Lead import uses phone number and external_id for deduplication. Existing leads are updated (empty fields filled) rather than duplicated.
Use the Usage API to pull per-account conversation and message counts. You can bill your customers based on these metrics however you choose — per conversation, per message, flat fee, or bundled into your existing pricing.
Yes. Use the view parameter when generating embed tokens to show only conversations, leads, sequences, or settings. You can also embed multiple views in different parts of your app.
All data is encrypted at rest (AES-256) and in transit (TLS 1.2+). Sub-account data is fully isolated at the database level — no shared tables, no cross-account queries. Recover is TCPA and CASL compliant with built-in opt-out handling. For Canadian partners, all personally identifiable information is handled in accordance with PIPEDA requirements. SOC 2 Type II audit is in progress.
All data is hosted on AWS and Supabase infrastructure in the United States. If you have data residency requirements (e.g., Canadian data must stay in Canada), contact us to discuss regional hosting options.

Support