Often, yes. Calls can be forwarded or routed for all hours, overflow or a selected schedule. The final setup depends on the current carrier and phone configuration.
Yes. Overflow rules can send calls to AiDial after the business's chosen condition. The caller then follows the same approved message, booking or routing process.
It can provide approved opening information, take a message, capture a booking request or follow an urgent-contact rule. The business decides which actions are available outside normal hours.
Complaints, negotiations, sensitive account decisions and requests that depend on professional judgement should remain with people. The agent can collect a brief reason before handover if that is appropriate.
It can make a booking only when a supported system, suitable appointment type and approved rules are configured. Otherwise it records the request for staff confirmation.
The workflow collects the minimum fields staff need, such as the caller's name, contact method, reason and preferred follow-up time. Different call types can require different fields.
The business supplies the urgent language, destination and unavailable fallback. The agent follows that rule and does not assess the seriousness of a situation itself.
Yes, where the business provides a transfer or callback path. The workflow should state clearly what happens when the intended person is unavailable.
Use recent call examples and select a small group with a clear outcome. Calls that regularly need exceptions or judgement are poor first candidates.
Yes. Sales, service, accounts and urgent calls can use separate destinations, hours and fallback actions.
Approved identity checks can be added for protected actions. If the check does not produce a safe match, the agent takes a restricted message or transfers the call.
A scoped AiDial project can use Australian hosting. The business should document which recordings, transcripts, summaries or outcome fields are kept and for how long.
No. Recording and transcription can be enabled or disabled for the project, with an approved consent and fallback process.
It can connect where AiDial supports the system and the required operation. API access, approved fields and failure handling are checked before launch.
Check whether messages contain the right details, bookings are confirmed correctly, transfers reach the right place and staff need to repair outcomes. Caller drop-off is also important.
Published plans are based on usage allowances. Call volume, duration, concurrent demand and any custom integration determine the suitable starting scope.