Describe your front desk
Share your property count, customer channels, booking flow, team handoffs, and the work you want Chronicle to handle.
Enterprise
One accountable front desk across your organization.
Bring calls, messages, booking requests, and customer context into one operating model, with the access, provider ownership, human approvals, and deployment controls larger teams need.
Access
SSO + RBAC
Connectors
Customer-owned
Workflows
Up to 500
Volume
No overage meter
Deployment scope
What we review before launch
- 01Included
Who can sign in and change rules
Review identity, access, and operator permissions before launch.
- 02Customer-owned
Which provider accounts carry messages
Agree which customer-owned accounts connect to the front desk.
- 03Agreed during setup
How retention and region requirements apply
Document retention and region requirements in the deployment scope.
- 04Technical review
Whether a dedicated deployment is needed
Review dedicated deployment requirements with the technical team.
01 / Operating controls
Choose who can access, connect, and approve.
Enterprise controls are reviewed before launch, so your team knows which identities, provider accounts, and data requirements are in scope.
Control 01 — Sign-in and rolesUse your identity provider and give people the access their work requires.
Enterprise includes single sign-on and role-based access control. During setup, your team maps who can administer Chronicle, review work, and change operating rules.
Single sign-onRole-based accessAdmin boundariesReviewed during setup
Control 02 — Provider ownershipConnect provider accounts your organization controls.
Use supported phone, messaging, and email provider accounts and credentials owned by your organization. Provider terms and availability still apply.
Customer-owned credentialsSupported communication routesWrite-only secretsProvider terms still apply
Control 03 — Retention and regionSet retention and region requirements before launch.
Enterprise includes retention and region controls. Your requirements are reviewed during deployment design and documented in the agreed scope.
Retention requirementsRegion requirementsData-flow reviewDocumented scope
Control 04 — Deployment reviewReview whether a dedicated deployment fits your environment.
A dedicated Chronicle deployment is an eligible option, not an instant default. Chronicle reviews the technical requirements with your team before it is commissioned.
Technical reviewDeployment eligibilityEnvironment requirementsAgreed scope
02 / Organization roles
Clear answers for every team.
Operations, service, IT, and procurement can review the same product boundaries before rollout.
Operations leaders
Give every location the same front-desk rules without hiding decisions.
- Set consistent rules for calls, messages, and booking requests across locations.
- Keep exceptions and uncertain work in a human approval path.
- See customer context and operational activity in one place.
- Use fair-use capacity without an application-level conversation overage meter.
One operating model, with local teams still in control.
IT & security
Bring access and provider ownership under your existing controls.
- Connect single sign-on and assign role-based access.
- Use customer-owned supported connectors for phone, messaging, and email.
- Review retention and region requirements during deployment design.
- Assess dedicated deployment eligibility in a technical review.
Your identity, provider, and deployment requirements stay explicit.
Customer service
Keep customer conversations connected when channels and shifts change.
- Carry customer context across supported calls and messages.
- Use configured rules to triage requests and draft the next step.
- Route uncertain or consequential work to a person before delivery.
- Coordinate booking requests through configured calendar connections.
Routine requests move forward; exceptions remain visible.
Legal & procurement
Know what is included, what needs review, and who remains responsible.
- Start from a published monthly price and defined plan entitlements.
- Use operational records for policy results, approvals, and delivery attempts.
- Keep provider and customer responsibilities explicit.
- Record deployment-specific controls and commercial terms in the order form.
Clear product boundaries before a commercial commitment.
03 / Plan details
Plan details you can verify.
Published entitlements and explicit responsibility boundaries make it easier to assess Chronicle before you commit.
- AuthorityHuman-gated
Policy can hold uncertain or consequential work for an authenticated operator.
- AccessSSO + RBAC
Single sign-on and role-based access control are Enterprise entitlements.
- Control
Chronicle handles routine front-desk work inside rules your organization sets. Work outside those rules stays with your team.
Chronicle / Enterprise operating boundary - ConversationsNot metered
No application-level conversation overage product. Fair-use, provider, infrastructure, and contract controls still apply.
- Workflows500
Workflow definition limit, with no application-set numeric limit on active Enterprise workflows.
- SupportSLA design
Enterprise support tier; final support commitments belong in the agreed terms.
04 / Commissioning
A reviewed path to launch.
Start with the front-desk work you need covered, then agree the providers, controls, and human handoffs before onboarding.
Review controls and providers
We review identity access, connector ownership, retention and region requirements, and whether a dedicated deployment needs technical review.
Agree scope and onboard
Once the scope is agreed in an order form, we configure the approved routes and begin onboarding with the human checkpoints you selected.
05 / Next step
Enterprise starts at $600 per month.
Send your channels, property count, controls, and technical needs. Paid service begins only after scope is agreed in an order form; provider, infrastructure, fair-use, and contract controls still apply.
Deployment review
Review your front desk with our team.
Share your channels, property count, identity provider, and compliance requirements. We review whether Chronicle fits your operational controls before any paid commitment.
What happens next
- 01We review your channels and customer routing requirements.
- 02We review your provider connectors and identity provider.
- 03We confirm scope in an order form before any billing begins.