Preparing an assistant
The Features and How it works pages explain draft agents, approved knowledge and the intended path to live calls. Start there if you want to understand which configuration decisions you can prepare today.
A few useful answers about the platform, service options and what is coming next.
An AI telephone assistant platform designed to answer business calls, use approved knowledge and perform permitted tasks in connected business systems.
Live telephone calling is still in development. The current application supports workspace registration, draft agent configuration, provider settings and a manual knowledge base.
Business integrations are not yet live. WHMCS is the first planned integration, with WooCommerce and Shopify following the core platform.
All-in-one is designed for managed telephone and AI services. BYOK uses your own Twilio account, phone number and OpenAI key, with provider bills paid directly by you.
The planned integration engine will support explicitly authorised tasks. Sensitive information and actions require server-side permissions and appropriate caller verification before use.
Human transfer and fallback are part of the voice roadmap. Transfer destinations and business-hour rules must be tested before an agent handles live calls.
Commercial pricing, included minutes and top-up rates are being finalised. You can discuss your requirements through the contact page.
Use Get Started to open registration in the connected Laravel application. You can create your workspace and begin configuring draft agents.
Yes. The development application supports draft agents with distinct roles and instructions. Prepare separate sales, support or billing roles when their knowledge and boundaries differ. Draft agents are not active telephone services.
Start with current service descriptions, public policies and answers your team already gives to common questions. Keep articles focused and review them before approval. Do not put API keys, passwords or private customer records into general knowledge articles.
No. Saved BYOK credentials are stored for configuration and remain unverified. Provider validation, telephone routing and the live voice engine need to be completed before an agent can receive calls.
Existing-number routing and forwarding are part of the telephone setup requirements. Discuss your current provider and the desired routing before changing your number. The current frontend does not provision or transfer telephone numbers.
Recording and transcript workflows are planned, with separate notices and retention controls required before live use. The marketing website does not itself record calls to the advertised contact number.
The intended live experience needs a fallback for missing records, expired credentials and provider outages. It should explain a next step and offer an appropriate human route. That behaviour still requires implementation and live testing.
No. It prepares an email draft in your browser. You choose whether to open and send it through your email application, or copy the prepared text. The frontend does not submit or store the enquiry.
Call 07777777777 to ask, or prepare an enquiry on the contact page. Useful details include the calls you receive, the tools you use and whether you prefer a managed setup or your own provider accounts.
Use the product pages to explore the part of the experience that matters to your business.
The Features and How it works pages explain draft agents, approved knowledge and the intended path to live calls. Start there if you want to understand which configuration decisions you can prepare today.
The Pricing page compares the planned managed approach with BYOK. It explains provider responsibility and the requirements that influence a setup. Commercial prices and paid subscriptions are not yet available.
Read the Security page for implemented controls and planned safeguards. Privacy and Terms explain the current development service, with the remaining launch decisions clearly identified.
Build an assistant around the way your business works.