Run each client service with a clear operating agreement.

Keep client scope attached to the work

List the client's source set, connections, records, staff roles and action destinations. Check the intended client identity at each boundary.

Include an unrelated-client access attempt in controlled acceptance tests. A shared agency view must still respect the permissions agreed for each client.

Confirm the actual workspace and role behavior in the configuration under review. This guide does not promise a particular seat model or plan entitlement.

Assign support and business decisions

The agency may investigate a failed connection while the client decides whether to waive a policy. Those tasks need different owners.

Record the receiving person, fallback route, agreed support hours and what happens when neither party is available. The agency responsibility guide provides a starting matrix.

A clear agreement also identifies who may pause a service and how ordinary incoming work is handled during that pause.

Review cost and scope together

Track support, defects, routine updates and new implementation separately. Usage costs alone do not describe the effort needed to maintain a client service.

The service-cost guide includes hypothetical calculations. The scope-change guide helps classify a new request before accepting it into an existing fee.

Verify tariffs, payer arrangements and included features separately; no commission or margin promise is made here.

Prepare for handover and exit

Maintain an inventory of configurations, accounts, sources and pending work. Name the receiving owner and test a controlled request before the handover ends.

The offboarding guide distinguishes transferred assets, provider revocation, retained data and continuing charges.

Bring the first client's roles, access cases and support boundary to an evaluation.

Client workspaces, branding and connected tools

Each client has its own workspace with role-based access, and a client's data can be exported or removed when you offboard them.

Agencies can present Vora under their own brand; resale and billing terms depend on your plan.

Vora connects natively to selected tools; each integration lists the actions it supports. Confirm these against the services you plan to run for each client.

Prepare one workflow and its support route

Prepare one workflow, its approved sources, expected result and handoff owner. Confirm the support route for that configuration.

Evaluate the configuration against one client workflow and its provider requirements. Discuss platform access, metered usage and external service charges for the configuration you need, and confirm inclusions and payer responsibilities in the quote. See the pricing guide.