Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.eolasflow.ai/llms.txt

Use this file to discover all available pages before exploring further.

Enterprise features let agencies and resellers white-label the platform, manage client organizations, set custom pricing, and bring their own API keys. Navigate to Enterprise in the Manage section to access these features.
Enterprise features require an Enterprise subscription plan. Contact sales@eolasflow.ai to upgrade.

​
Enterprise Dashboard

The Enterprise overview page gives you a high-level view of your reseller operation:
  • Sub-Organizations — Total number of client orgs you manage
  • Credits Allocated — Combined credits distributed to all sub-orgs
  • Branding Status — Whether white-label branding is active and published
  • Quick Links — Jump directly to Branding, Sub-Organizations, and Rates configuration
Use this page as your starting point before diving into individual sub-org management.

​
White-Label Branding

Replace all EolasFlow branding with your own across the entire dashboard for your users.
1

Navigate to Branding

Go to Enterprise → Branding in the Manage section.
2

Set Company Name & Tagline

Enter your Company Name and Tagline. Your brand replaces “EolasFlow” throughout the dashboard for all users in your sub-orgs.
3

Upload Logo

Upload your Logo (PNG, JPEG, SVG, or WebP — max 2 MB). Your logo appears in the sidebar, outgoing system emails, and the login screen.
4

Upload Favicon

Upload a Favicon to replace the browser tab icon. Square images (32×32 or 64×64 px) work best.
5

Configure Color Theming

Set a Primary Color and Accent Color. These are applied across the entire dashboard UI for your sub-org users.
6

Configure Email Settings

Set the Sender Name, Support Email Address, and Reply-To Address used in all system emails sent on your behalf (call summaries, invites, alerts).
7

Preview & Publish

Use the live Preview to see exactly how the branding looks before making it visible to users. When satisfied, click Publish.
Always use the preview before publishing. Check the sidebar, email headers, and login screen to make sure logos and colors look correct at all sizes.
You can reset to EolasFlow defaults at any time using the Reset to Defaults button. This does not delete your uploaded assets — you can re-publish them later.

​
Sub-Organization Management

Sub-organizations let you give each client their own fully isolated workspace. Perfect for agencies managing multiple clients under a single Enterprise account.
1

Navigate to Sub-Organizations

Go to Enterprise → Sub-Organizations.
2

Create a Sub-Org

Click Create Sub-Org, enter the organization name, and invite the initial admin by email.
3

Admin Accepts Invite

The invited admin receives an email and sets up their account. They become the owner of that sub-org.
4

Sub-Org is Ready

The sub-org is now an independent workspace. The admin can invite their own team members and start building.
Each sub-org is completely independent:
  • Own resources — Assistants, VoiceFlows, contacts, conversations, and phone lines are isolated per sub-org
  • Inherited branding — Sub-orgs automatically use your published white-label branding
  • Data isolation — Members invited to a sub-org only see that org’s data — never other clients’ data
  • Separate billing — Each sub-org draws from its own allocated credit balance

​
Credit Management

Credits flow from your parent organization’s pool down to each sub-org’s individual balance.

​
How Credit Allocation Works

  1. Your parent org holds the master credit pool (purchased via the Usage page)
  2. You allocate portions of that pool to individual sub-orgs
  3. Sub-orgs consume credits from their own allocation as calls are made
  4. The parent org dashboard shows each sub-org’s remaining balance and consumption

​
Allocating Credits

1

Open the Sub-Org

Go to Enterprise → Sub-Organizations and click on the sub-org you want to fund.
2

Add Credits

Click Add Credits, enter the amount to transfer, and add an optional description (e.g., “March allocation”).
3

Confirm Transfer

Confirm the transfer. Credits move immediately from the parent pool to the sub-org balance.
Set up low-balance alerts for each sub-org so you’re notified before a client runs out of credits mid-campaign. Monitor sub-org usage from the parent dashboard on a weekly cadence.

​
Rate Overrides

Set custom per-component rates for each sub-org to control your reseller margins. Rates are defined per direction (inbound and outbound) and per AI component.
ComponentDescription
PlatformBase platform fee per minute of call time
STTSpeech-to-text transcription cost per minute
LLMLanguage model inference cost per minute
TTSText-to-speech synthesis cost per minute

​
Setting Rates

  1. Go to Enterprise → Sub-Organizations and open a sub-org
  2. Click the Rates tab
  3. Set custom rates for each component and direction (inbound / outbound)
  4. Use the Markup field to add a percentage on top of the base rate — this becomes your margin
  5. Select the sub-org’s Currency — exchange rate conversion is applied automatically
Rate changes apply to future calls only. They are not applied retroactively to calls already completed or currently in progress.

​
Provider Restrictions

Control which AI providers and platform features each sub-org can access. Start restrictive and open up as clients grow.
Limit which voice pipeline modes the sub-org can use:
  • OpenAI Realtime — GPT-4o native audio pipeline
  • Gemini Live — Google’s native audio pipeline
  • Custom — Modular STT + LLM + TTS pipeline
Restricting to a single pipeline simplifies support and keeps costs predictable.
Control which language models the sub-org’s assistants can use:
  • OpenAI (GPT-4o, GPT-4o mini, etc.)
  • Groq (Llama 3.3, etc.)
  • Gemini (Flash, Pro)
Restrict to providers you have negotiated rates for or have BYOK keys configured.
Control which text-to-speech voices are available to the sub-org:
  • ElevenLabs
  • Cartesia
  • Google TTS
  • OpenAI TTS
Limit to providers included in your rate overrides to avoid unexpected costs.
Set hard limits per sub-org:
  • Phone Numbers — Maximum phone lines the sub-org can purchase
  • VoiceFlows — Maximum VoiceFlow (campaign) configurations
These limits prevent a single sub-org from over-consuming shared resources.
Start with conservative restrictions when onboarding a new client. As you understand their usage patterns, you can open up providers and increase limits from the Enterprise dashboard.

​
BYOK (Bring Your Own Keys)

Use your own provider API keys instead of EolasFlow’s shared pool. When BYOK is active, the corresponding component cost is zero — you pay the provider directly at your negotiated rate.
1

Navigate to API Keys

Go to Organization → General and scroll to the API Keys section.
2

Add Provider Keys

Click Add Key for the providers you want to configure. Supported providers:
ProviderUse
OpenAILLM + TTS + Realtime pipeline
DeepgramSTT
ElevenLabsTTS
GroqLLM
GeminiLLM + Live pipeline
CartesiaTTS
SarvamSTT + TTS (regional languages)
PineconeKnowledge base vector storage
3

Verify Key

Paste your API key and click Verify. EolasFlow tests the key and confirms it is valid before saving.
4

BYOK is Active

Once saved, calls using that provider draw from your key. The component cost for that provider drops to zero in your credit usage.
BYOK requires an Enterprise plan. Keys are stored encrypted and are never displayed in full — only the last 4 characters are shown after saving.
BYOK is especially valuable for high-volume sub-orgs. Negotiating direct rates with OpenAI or ElevenLabs at scale can significantly reduce your per-call cost compared to the platform’s shared rates.

​
Best Practices

  • Start with one sub-org — Test the complete flow (create, brand, allocate credits, run a call) before onboarding real clients
  • Set conservative provider restrictions initially — Open up access as you understand each client’s needs
  • Use rate markup for healthy margins — Set markup per component so every call contributes to your reseller margin
  • Monitor sub-org usage weekly — Catch unusual spikes early before a sub-org’s balance runs out
  • Keep branding consistent — Upload high-resolution logos (at least 200×200 px for the logo, 64×64 px for the favicon) to avoid blurry assets across screen sizes

​
Next Steps

Organization Settings

Configure your parent org, team members, and Twilio credentials

Usage & Credits

Purchase credits and monitor consumption

Phone Lines

Purchase and manage phone numbers for your sub-orgs