What is an "action"?
The volume actually consumed is measured in tokens (the technical unit of language processing), never cut off abruptly on the Nth attempt. "Action" is an indicative equivalent — about 33,000 tokens on average, including dictation and transcription — shown to keep things readable, not a contractual guarantee or a turn-by-turn counter. Confirmations, cancellations and local lookups consume no tokens. The real balance (tokens and action equivalent) is shown in the module before any use and before any purchase.
Why an annual plan rather than a one-time purchase or a monthly subscription?
SpeakDo includes a PWA, a middleware, voice and language processing, hosting, and ongoing updates. Annual billing funds a maintained service while limiting micro-transactions, processing fees and the number of invoices — a deliberate choice, not a temporary technical constraint.
Do the plans cap the number of users?
No. Mentions like "recommended for 1 user" or "about 3 regular users" are volume references, not technical caps. Credits are pooled across all users of the same SpeakDo account; a team can very well split the included volume among several people whose individual usage stays occasional.
Do I need to create an OpenAI or OVH account, or install Ollama?
No. The processing engine and transcription are already built into the SpeakDo service and included in the plan. No API key and no GPU server are required.
Where does payment happen?
Never on this page, nor in daily field use. Once the uses included in the trial are exhausted, the administrator opens a subscription page tied to their tenant from the Dolibarr module.
Is the price the same for all ERP integrations?
Today, Dolibarr is the only integration actually available, and these plans apply to it. See the Integrations page for the architecture planned beyond Dolibarr.