Run a support application for multiple companies
Status: Upcoming — not yet available.
Section: DOC-PF-customer-management#overview.
Let Acme and Northwind use the same support application while keeping each company's conversations, files, connected accounts and usage separate. Add each company as a customer, identify it on application requests, and keep serving the others when one leaves.
Availability: this is the upcoming Platforms experience. The customer-management API and platform management console are not yet available; the steps below describe the selected workflow without installation commands or executable requests.
Before you start: choose the workspace and project for your application and decide whether you host each company as a customer or operate in a workspace it owns. Collecting payments from your customers remains the responsibility of your own billing system.
Add the first company to your application
Status: Upcoming — not yet available.
Section: DOC-PF-customer-management#customer-relationships.
For the hosted application in this recipe, add Acme as a customer inside your Travila project. Save its customer identity with the Acme account in your application. Adding the customer does not create a separate Travila workspace or subscription.
Follow setup until the customer is ready before enabling its traffic. If the response is interrupted, use the original request's recovery flow instead of creating another Acme account. Then add Northwind the same way, with its own identity.
A different arrangement applies when Acme already owns a Travila workspace and wants you to work there. Keep that workspace independent and request delegated access. Paying for the workspace does not itself give your platform access to its content.
Route each signed-in company to its own data
Status: Upcoming — not yet available.
Section: DOC-PF-customer-management#customer-isolation.
Resolve the company from your application's authenticated account and use its customer identity on each request. Use Acme's identity for its support conversations and files; use Northwind's identity for Northwind's work.
Verify the separation with a controlled test: upload a different invoice.pdf for each company, then list files as each customer. Acme receives its copy and Northwind receives its own. Keep the same customer identity across test and live while using each mode's separate data; Acme's test conversation does not appear in live history.
Where an operation permits an omitted customer, it selects only records that are unassigned. It does not request all customers' data. Use explicit, separately authorized combined reads when your application needs that view.
Support a client that owns its own workspace
Status: Upcoming — not yet available.
Section: DOC-PF-customer-management#delegated-workspace-grants.
When Acme wants your service to operate in its own workspace, ask its administrator to authorize the required work. For a reporting integration, request usage-reading permission rather than permission to change resources.
The administrator selects the project, test or live mode, any relevant customer accounts, allowed actions and expiry. Configure your integration to use that grant together with its own permitted API key; the grant does not expand what that key can do.
Make one permitted reporting request and confirm the intended scope before enabling routine work. Acme can later review or revoke your access. Revocation stops new work that depends on the grant and identifies outstanding actions already sent to external services. An invitation or sign-in link does not provide permanent access.
Give your operations team a client health view
Status: Upcoming — not yet available.
Section: DOC-PF-customer-management#managed-console-boundary.
Use the platform console to review the permitted usage totals and service status for client-owned workspaces. This lets your team notice a usage change or service issue without opening the client's employee conversations.
Give the team the summary it needs for support and billing. Individual users, conversations and transcripts are not exposed through console drill-down, exports or embedded sessions. A person who needs the client's own console must receive membership and permissions from that client; managing the integration or paying the bill does not supply that access.
Reconcile each company’s usage
Status: Upcoming — not yet available.
Section: DOC-PF-customer-management#usage-and-payment-attribution.
Use the customer's attributed usage and applicable agreement to reconcile the charges for your application. Adding a customer or a test/live mode has no separate entity fee in this design; metered usage and accepted project or commercial terms still apply.
When a payer arrangement changes, agree the effective date and retain the earlier agreement for earlier usage. If Acme takes responsibility for charges from that date, a usage record that arrives later still belongs to the agreement in effect when the usage occurred.
Use these records alongside your own customer billing system. Travila attributes usage but does not collect your customers' payments in this workflow. See commercial agreements and invoicing for your agreement with Travila.
Recover signup and offboard one company
Status: Upcoming — not yet available.
Section: DOC-PF-customer-management#relationship-recovery.
If the connection drops while adding Acme, check the original request. Travila returns Acme's existing customer record if creation finished, its progress if setup continues, or the creation failure. Retrying the same request returns that outcome rather than adding Acme twice. Your application can continue setup from the confirmed result.
When Acme leaves your service, delete that customer and follow cleanup. New work stops for Acme, while Northwind keeps using the application. Show cleanup progress, records retained with their reasons, and any action already sent to an external service that is awaiting confirmation.
Finish the offboarding task when the requested cleanup is accounted for. Delayed updates do not reactivate Acme, and deleting it does not close a shared payment account. Keep the usage and payment references needed to reconcile outstanding charges. See billing and spend for charge history.
Document ID: DOC-PF-customer-management. Section identities and revisions.