Legal / 06
Acceptable Use
What you may run on Avaga numbers, inboxes, APIs, and AI employees. Ordinary business use, not abuse.
Last updated 26 September 2026
1. Purpose
Avaga Workspace is for ordinary business communications: a staffed line, a shared inbox, recordings, Assist Pro, and AI employees that sit next to your team. This policy is the line between that use and abuse.
It sits with the Terms of Use. We can suspend a workspace that breaks it. Carriers can block traffic even when we have not yet emailed you.
2. Ordinary business use
Unlimited US and Canada inbound and outbound calling is for ordinary business use. Terms of Use apply. High-volume short-duration calling, traffic pumping, origination that exists only to terminate, and similar patterns are not ordinary.
Additional international bundles exist. MMS is only available for US, Canadian, and Australian numbers. If your use case is a contact center of a different shape, talk to sales before you assume a published unlimited line will hold it.
3. Consent, recording, and messaging
You must have permission to call, text, record, and transcribe. You must play or show the disclosure your jurisdictions require. Pause before cards and identity documents. Resume after.
WhatsApp, SMS, MMS, Messenger, and Instagram are not a loophole around consent. Platform rules still apply. Do not import a purchased list onto an Avaga number and hope.
4. Prohibited traffic
Do not use Avaga to send spam, phishing, malware, or social-engineering lures. Do not impersonate a bank, a government, or a person. Do not harvest personal data from the inbox for a purpose the caller did not accept.
- Unlawful threats, harassment, or content that exploits children
- Calls or messages that evade caller ID, STIR/SHAKEN, or similar rules you are subject to
- Auto-dialed sales campaigns that ignore do-not-call and consent rules that apply to you
- Using an AI employee to pretend it is a licensed clinician, lawyer, or advisor
- Uploading malware through forms, MMS, or API payloads
5. AI employees on this policy
You may hire receptionist, sales, support, booking, and lead-manager seats to cover the jobs those names describe. You may not instruct them to invent medical, legal, or financial outcomes. You may not hide that a caller can reach a human.
Test barge-in before you promote. If a person cannot take the line with the transcript attached, the seat is not ready. Details live in the LLM Policy.
6. API, webhooks, and forms.js
Use the API, webhooks, messaging API, and avaga-forms.js to write into the workspace brain. Do not scan, scrape, or load-test production without written permission. Do not share workspace keys in public repos. Rotate a leaked key.
Custom integrations that the public API cannot cover are an Enterprise conversation, not a loophole in this policy.
7. Resale and sharing
Do not resell seats, numbers, or AI employees except under the Channel Partner track. Do not put a single owner login on a client floor you do not operate. Affiliate partners refer. They do not open a workspace in the buyer's name without authority.
8. Security of your floor
Keep 2FA on for owners and admins. Use roles. Do not grant every agent the archive. If you forward to mobile, you still own the recording and the device. Report a suspected compromise to hello@avaga.io.
9. Enforcement
We may warn, throttle, suspend numbers, suspend AI employees, or close the workspace. We may keep records needed to explain the action to a carrier or a regulator. You remain responsible for usage billed before the suspend.
10. Reports
If you received abusive traffic from an Avaga number, write hello@avaga.io with the DID, time, and a recording or screenshot if you have one. We will not discuss another customer's floor with you beyond what we must.
Related: Legal desk · Privacy · Data deletion · Security · Compliance & BAA