Frequently asked questions about IVR, AI voicebots and our services

An IVR is a system that greets callers, offers choices by keypad (DTMF) or by voice, and then routes them to the right team or gives them information automatically. A custom IVR can also query your databases to personalize the call flow for each caller.

An AI voicebot, sometimes called a callbot or voice agent, is a conversational agent that works over the phone. It combines speech recognition, language understanding and speech synthesis to hold a natural conversation, answer questions and complete tasks such as booking an appointment or tracking an order.

A traditional IVR guides callers through a structured menu with predefined options. A voicebot understands requests phrased in the caller's own words and carries a conversation. The two often work together: a single call flow can combine menus, speech recognition and a conversational agent depending on the use case.

It depends on scope: the number of call flows, the integrations required, security requirements and call volume. After a free 30-minute consultation, we propose a project plan and timeline tailored to your situation.

Yes. We have long experience with Asterisk, AGI and ARI, as well as FreePBX and SIP environments. We can connect to your current infrastructure through SIP trunks or application-level integrations, without forcing you to replace everything.

Yes. We connect telephony to CRMs such as Salesforce, HubSpot or Dynamics, as well as ERPs, databases and internal APIs. That lets the system identify callers, show their record to agents and log interactions automatically.

We routinely build call flows in English and French, including fully bilingual services. Other languages are possible depending on the speech recognition and synthesis engines selected, which we validate with you during design.

We apply data minimization, encrypt communications, restrict access and define retention periods. We help you document processing activities to meet Law 25 and other applicable frameworks such as PIPEDA; because exact obligations depend on your context, we recommend confirming them with legal counsel.

As a rule, callers must be told that the call is being recorded and why, and some situations require explicit consent. We build the disclosure messages and, where needed, opt-out options into your call flows. Rules vary by jurisdiction and use case, so legal advice is worthwhile.

Several options are available: in the cloud, on your own servers (on-premise) or in a hybrid setup. The right choice depends on your security, data residency, availability and cost requirements, and we recommend the option that fits best.

Yes, and it is essential. The voicebot hands off the call when a request falls outside its scope, when the caller asks for a person, or based on rules you define. The context it has gathered can be passed to the agent so the customer does not have to repeat themselves.

Pricing depends on scope: the number of call flows, integrations, call volume, hosting and support level. We prepare a tailored quote after the free 30-minute consultation, once we clearly understand your needs.