This page documents how consent is obtained before any message is sent through Audivice.ai, what the recipient hears or reads at the moment they agree, and what record is kept. It exists so recipients, our business customers, our messaging providers, and mobile carriers can verify the process.
Program name: Audivice.ai Meeting Link Delivery
Platform operator: NXR Capital LLC.
Address: 3141 N 35th Ave, Phoenix, AZ 85017, USA
Support: support@audivice.ai · +1-602-362-8881
1. Who sends, who consents
Audivice.ai is software used by warehouses, distributors, and suppliers to run sales calls with their buyers. Those businesses schedule meetings with their own customers and existing trade accounts.
- The business speaks with the buyer, obtains consent, and is the sender of record.
- Audivice.ai transmits the message on that business's behalf and under contract.
- Every message names the business it comes from.
Audivice.ai does not build, buy, rent, or purchase contact lists, and no message is ever sent to a number that does not have a consent record attached.
2. Two separate consents, asked separately
Every call involves two distinct permissions. They are asked at different moments and recorded separately, so each can be verified on its own.
a. Recording consent, at the start of the call
Before recording begins, the representative states:
"Before we start - this call is being recorded and transcribed so we can prepare your quote and meeting details accurately. Is that alright with you?"
Recording proceeds only on an affirmative answer. Several jurisdictions require the consent of all parties to a recorded call, and representatives are trained and contractually required to give this disclosure on every call regardless of where the recipient is located.
b. Messaging consent, when the meeting is scheduled
When a meeting is agreed, the representative asks:
"I can send you the link for our meeting on [date] by text, WhatsApp, or email - which do you prefer? If you'd like it by text, message and data rates may apply, and you can reply STOP anytime to opt out."
Consent is recorded only where the recipient names a messaging channel or gives an affirmative answer. Silence, ambiguity, or "whatever's easiest" is not treated as consent; the representative asks again or defaults to email.
Language
Representatives deliver both disclosures in the recipient's preferred language. The language used is stored with the consent record, along with a translation of the consent exchange for audit. Opt-out keywords in that language are configured alongside the standard English keywords, and auto-replies are returned in the language the recipient was consented in.
Written alternative
Where the number is supplied in writing instead - in a booking confirmation, an email reply, or a form the business provides - the same disclosures appear next to the field:
By providing your mobile number you agree to receive your meeting link and related scheduling messages by text, WhatsApp, or RCS from [Business Name], delivered via Audivice.ai. Message frequency varies. Message and data rates may apply. Reply STOP to cancel or HELP for help. Consent is not required to attend the meeting or to do business with us.
3. Consent is never required
If the recipient declines, or does not answer clearly, the meeting link is sent by email and the meeting proceeds normally. Messaging consent is not a condition of attending the meeting, receiving a quote, placing an order, or maintaining a trade account.
4. What we record for every consent
Audivice.ai transcribes the calls its customers run. When the consent exchange occurs, the following is captured and stored against the contact:
| Field | Source |
|---|---|
| Mobile number in E.164 format | Entered or confirmed on the call |
| Channel agreed (SMS, WhatsApp, RCS, or email) | The recipient's answer |
| Date and time of consent (UTC) | Call timestamp |
| Representative and business account | Call metadata |
| Recording consent given (yes/no, timestamp) | Call transcript |
| Messaging consent given (yes/no, timestamp) | Call transcript |
| Transcript excerpt of each consent exchange | Call transcript |
| Language of the exchange, plus translation | Call transcript |
| Call recording identifier | Call record |
| Script version and language presented | Application config |
For written consent, we store the number, timestamp, IP address, the page or message where consent was given, and the exact text displayed.
Screenshot: ⟦screenshot of the consent record as it appears in the Audivice.ai dashboard: number, channel, timestamp, and the transcript excerpt. This is the artifact a carrier reviewer will look at.⟧
Screenshot: ⟦screenshot of the consent confirmation step a representative completes before a number becomes messageable.⟧
The system blocks sending to any number without a valid consent record. There is no manual override and no bulk import path that bypasses this check.
5. First message and message types
The first message a recipient receives identifies the business, states the purpose, and carries opt-out instructions.
| Type | Example |
|---|---|
| Meeting link (first message) | [Business Name]: You asked on our call today for the link to our meeting Tue Sep 22, 2:00 PM CT. Join: https://links.audivice.ai/m/ab12cd Reply STOP to opt out, HELP for help. |
| Reminder | [Business Name]: Your meeting starts in 30 min. Join: https://links.audivice.ai/m/ab12cd Reply STOP to opt out. |
| Reschedule | [Business Name]: Our call moved to Wed Sep 23, 10:00 AM CT. New link: https://links.audivice.ai/m/ef34gh Reply STOP to opt out. |
| Cancellation | [Business Name]: Our call Tue Sep 22 is cancelled. We will be in touch to reschedule. Reply STOP to opt out. |
The first message states why the recipient is hearing from us rather than asserting that they consented. The registered business name leads every message.
Message bodies are restricted to the GSM-7 character set. Em dashes, curly quotes, ellipsis characters, and emoji force UCS-2 encoding, which cuts the segment size from 153 characters to 67 and inflates both cost and delivery risk. Composition is validated before send.
Links are served from a branded Audivice.ai domain. We do not use public URL shorteners.
No marketing, promotional, or third-party content is sent through this program.
6. STOP and HELP
- Replying STOP (or END, CANCEL, UNSUBSCRIBE, QUIT) immediately ends all messages to that number and returns one confirmation.
- Replying HELP or INFO returns the program name, frequency disclosure, rate disclosure, opt-out instruction, and our support email and phone number.
- Replying START, UNSTOP, or SUBSCRIBE re-subscribes a number that previously opted out.
Keywords are handled automatically by our messaging platform on every channel, and an opt-out on one channel suppresses the number on all of them. Opting out does not cancel the meeting; the link is sent by email instead.
A recipient may also opt out by telling the representative, or by emailing support@audivice.ai.
7. Retention and production
Consent and opt-out records, including the transcript excerpt, are retained for at least ⟦X years⟧ after opt-out and can be produced on request to a carrier, messaging provider, regulator, or the recipient themselves.
8. Privacy commitment
Audivice.ai does not sell, rent, or share mobile phone numbers or messaging consent with third parties or affiliates for their marketing or promotional purposes. Numbers are disclosed only to the messaging providers and carriers that deliver the messages. Full detail is in our Privacy Policy.
9. Questions
Audivice.ai is a service of NXR Capital LLC.
NXR Capital LLC · 3141 N 35th Ave, Phoenix, AZ 85017, USA · support@audivice.ai · +1-602-362-8881