Give every connection a clear job.
Choose the work to bring into Revvalo and the specialist systems to keep. Map records, actions and ownership before the connection goes live.
| Connection | Action type | Scope / direction | Before you connect |
|---|---|---|---|
| CRM import | Import · user-assisted | Mapped records into Revvalo | Review fields, ownership, duplicates and a sample import. |
| Salesforce / HubSpot | Connected CRM work | Connection-dependent; confirm direction and objects | Agree the supported object/field matrix and conflict owner. |
| Connected mailbox | Draft / send / log | Drafts in Revvalo; delivery via authorized mailbox | Mailbox authorization, sending policy and review configuration. |
| Revvalo AI Voice | Call / transcribe / handoff | Provider-dependent inbound/outbound call work | Number, region, recording consent, usage and escalation policy. |
| Webchat Widget | Answer / capture / handoff | Website conversation into configured customer workflow | Knowledge, site embed, privacy notice and staffed handoff. |
| Marketing channels | Draft / schedule / publish | Content to the configured destination | Destination permissions and editorial approval. Confirm each channel action. |
| Browser extension | Capture · user-assisted | Supported browser context into CRM | Supported source pages, permissions and mapping; third-party terms apply. |
| API / webhooks | Read / write / handoff | Endpoint- and event-dependent | Authentication, tenant scope, supported event and retry ownership. |
| Staffing finance connections | Release / handoff | Approved work evidence to configured provider | Country, pay/bill scope and provider contract; release is not payment. |
| Construction finance connections | Commercial / financial handoff | Configured project and finance workflow | Contract approvals, claim/payment states and accounting ownership. |
This is a setup guide, not a universal object-by-object sync contract. Confirm exact coverage for the connection and selected package.
Consolidate with a reason.
Start with one customer workflow and identify the system that owns every record and action.
-
List the systems
Record the current source, destination and responsible team.
-
Agree the mapping
Specify objects, fields, direction and duplicate/conflict handling.
-
Inspect a synthetic sample
Test an ordinary action and a connection failure.
-
Assign the handoff
Document who resolves errors and how the result is recorded.
See your customer workflow, connected.
Bring one real workflow to the conversation. We’ll show how the records, agents and review points fit together.