Key points
- Subscribers use the supported Flowtix-managed outbound calling workspace instead of adding their own carrier credentials.
- Browser microphone permissions, calling eligibility, contact data, plan limits, and service availability all affect whether a call can start.
- Recording, consent, retention, and customer-contact rules remain the responsibility of the organization using the calling workflow.
How the current calling model works
Flowtix Cloud Calling is managed at the platform level. Subscribers do not need to connect or maintain their own carrier account in workspace Integrations for supported outbound calling.
Calling availability can still depend on the current plan, organization eligibility, number availability, provider health, and usage limits. A visible dialer does not override those controls.
Check the browser before the first call
The browser must be allowed to use the microphone for the Flowtix calling workspace. If microphone access was previously blocked, update the browser site permission and reload the page before retrying.
Use a stable network connection and avoid testing through restrictive browser privacy modes, VPN policies, or corporate firewalls that block real-time communications unless your environment has been validated for the calling workflow.
- Confirm microphone permission is allowed for flowtix.work.
- Confirm the intended microphone and audio output device are selected.
- Confirm the contact has a usable phone number and the workspace is eligible to call.
Treat caller identity and consent as operating requirements
Caller identity, recording consent, opt-out obligations, permitted calling hours, and other communication rules vary by jurisdiction and use case. Flowtix provides the workflow, but the organization must use it lawfully and follow applicable customer-consent requirements.
Review the Flowtix Recording Consent and Acceptable Use policies before relying on automated recording or high-volume calling.
Record outcomes and follow-up work
A completed call becomes more useful when the outcome, notes, recordings or transcripts where available, and the next follow-up action remain connected to the contact. Use tasks or opportunity updates instead of relying on memory after the call.
Troubleshoot a call that will not start
If a call does not start, first verify browser permissions, contact data, plan and trial limits, organization eligibility, and whether the calling service is currently available. Repeated clicking is not a useful recovery strategy and can make the user experience harder to interpret.
If those checks pass and calling still fails, use the official support channel with the approximate time, contact or workflow context, and what the interface displayed. Do not send passwords, secrets, or private provider credentials in a support request.
Need to continue from here?
Use the related product page for the next step, or contact Flowtix support if the workspace is not behaving as described in this current guide.