AI agents, chat and automation · For businesses evaluating 3CTel
What is a custom deployment, and when do I need one?
A custom deployment is how 3CTel handles requirements that a standard plan does not cover: keeping an existing PBX and adding cloud services through SIP trunking, call flows and AI agent behaviours designed for your process, number plans across several regions, requirements from a regulated industry worked through with you, and custom integrations. It is scoped, quoted and delivered as a project with a named specialist, and nothing is billed before activation.
When a standard plan is not enough
- Hybrid PBX. You own a PBX you want to keep, and need cloud calling, AI agents or Contact Centre features alongside it. SIP trunking connects the two.
- Bespoke call flows and agent behaviours. Routing that depends on data in your systems, AI agents that follow a multi-step process specific to your business, or hand-off rules that vary by client type.
- Multi-region number plans. Local numbers across several provinces or countries with routing, caller ID and 9-1-1 addresses managed per site.
- Regulated-industry requirements. Recording, retention, access and consent rules that your industry expects, handled with you and your advisors; 3CTel describes what it configures, not what it certifies.
- Custom integrations. Practice-management, broker-management or line-of-business software without a standard connector.
How a custom deployment is delivered
Discovery: a specialist maps your current set-up, call types, systems and constraints. Design: you receive a written plan covering call flows, agent behaviours, numbers, integrations and hand-off rules, with a quote. Build: the plan is configured and connections are developed. Test: everything runs on temporary numbers and a staging site with your team, and adjustments are made. Switch-over: numbers are ported or redirected and the system goes live. Review: a follow-up after go-live and the monthly optimization review continue from there.
What stays the same
A custom deployment uses the same platform, admin portal, apps and support as every other 3CTel account. What differs is the amount of design and integration work, and the delivery steps above. If your requirements later become standard, the deployment continues on the same account without a migration.
Related questions.
How do I know whether I need a custom deployment?
Describe your requirements to a specialist. If a standard plan and modules cover them, that is what is recommended. A custom deployment is proposed only where a specific requirement cannot be met otherwise.
Can we keep our existing PBX indefinitely?
Yes. SIP trunking lets the PBX place and receive calls through 3CTel while cloud features are added around it. Some customers migrate over time; others keep the hybrid set-up.
How long does it take?
It depends on the scope. The written plan includes a timeline, and testing on temporary numbers means your current service is not affected until switch-over.
Is it priced differently?
Yes. A custom deployment is quoted after discovery, with the design and integration work itemized. As with every 3CTel service, nothing is billed before activation.
Last updated:
Not a 3CTel customer yet? See your recommended setup in four short steps.
Build My Phone System