Phone and forwarding
Your business number stays. AKKIVO provides a destination number. Your carrier sends unanswered calls there after the delay you set. Verification in the workspace confirms the path before you rely on it.
Integrations
Your number, your knowledge, your calendar
AKKIVO does not replace your phone system or your files. It answers forwarded calls, uses the company knowledge you approve, and — once a calendar can be connected — books from that calendar.
In operation
What already meets your workflow
These three areas exist in the workspace. Calendar providers below have their own status, and not all of them can be connected yet.
Website and documents
Import the public pages of your company website, or upload PDF, Word, text, and Markdown. The assistant uses that material for hours, prices, services, and policies. Re-import or replace files when the source changes.Appointments
When a calendar is connected and assigned to the service, the assistant can offer times from that calendar. Until a provider is connectable in your workspace, appointments stay unassigned.
Calendar providers
What the catalog is built for
Status is per provider. In rollout means the product path exists and is not open for customer connection yet. Planned means the provider is in the catalog without a customer connection. Nothing in this list is a live connection until your workspace shows the provider as available.
Google Calendar
Sign in with Google (OAuth 2.0). Designed for availability and for creating, updating, and deleting events.In rollout
Microsoft 365 / Outlook Calendar
Sign in with Microsoft (OAuth 2.0). The same appointment actions as Google, once the provider is connectable.In rollout
Apple iCloud Calendar
CalDAV with an Apple app-specific password. You create that password in your Apple ID. It is not your regular iCloud password.In rollout
CalDAV
A server URL and credentials for a calendar that speaks CalDAV and is not one of the named providers below.In rollout
Nextcloud Calendar
Your Nextcloud CalDAV URL and credentials.Planned
Fastmail Calendar
CalDAV with a Fastmail app password.Planned
Zoho Calendar
Sign in with Zoho (OAuth 2.0).Planned
Yahoo Calendar
Sign in with Yahoo (OAuth 2.0).Planned
Microsoft Exchange Server
On-premises Exchange (EWS) credentials for organisations that do not use Microsoft 365.Planned
Proton Calendar has no supported connection path. The platform catalog marks it unsupported, and it is not offered in the workspace.
How it is used
Connect, assign, then book
A connection in the workspace applies to a service only after you assign that calendar under Appointments.
Step 01
Connect in the workspace
Workspace Integrations is where a provider is connected. OAuth providers open the vendor sign-in. CalDAV providers ask for the username, secret, and a server URL when the provider needs one.
Step 02
Assign it to the service
The workspace can hold the connection. The service uses it only after you assign that calendar under Appointments.
Step 03
Use real availability
Offered times should come from the assigned calendar. If the connection needs permission again, the workspace asks you to reconnect. Disconnect removes it from the customer view.
Put this on your line?
Start with the documentation for forwarding and knowledge. Calendar connection follows the status you see in the workspace.