A business using Noxtill determines the recipients, purpose and content of most customer communications and is responsible for having a lawful basis or valid consent where required. Noxtill provides tools to capture evidence, route messages, enforce preferences and audit delivery.
Noxtill may block, throttle, pause or reject messages/workflows that appear to violate law, provider rules, opt-out choices, complaint thresholds or the AUP.
For consent-dependent communication, Noxtill should retain evidence that answers:
- who consented;
- which business/brand identity was shown;
- what purpose was described;
- which channel was covered;
- exact text/version shown;
- when consent was granted;
- where/source it was collected;
- how it was captured;
- what evidence supports it; and
- when/how it was withdrawn, superseded or disputed.
A field such as marketing_opt_in=true is not sufficient evidence by itself.
Importing a customer, lead or contact does not create marketing consent. Imported lists should default to non-marketing unless lawful transferable evidence is imported and mapped to the person, purpose, channel, business identity and consent version.
Noxtill should require an import attestation. A business may still send genuinely necessary service messages where lawful, but may not treat an old customer database as a blanket permission for promotional WhatsApp, SMS or email.
Noxtill should classify messages by purpose and provider category.
Typical operational/utility examples: receipt, appointment confirmation, requested statement, delivery update, security notice, necessary subscription/account update, service reminder requested by the customer.
Typical marketing examples: discount, offer, re-engagement, product promotion, cross-sell, referral invitation and promotional newsletter.
A business must not add promotional material to an operational message merely to avoid marketing-consent rules.
Noxtill’s intended WhatsApp integration uses the official Meta WhatsApp Business Solution/Cloud API. Businesses must comply with current technical documentation, WhatsApp Business Solution Terms and the current WhatsApp Business Messaging Policy.
Customer replies flow into Unified Inbox. The user interface should check provider reply-window/template rules before rendering a free-form composer. If a free-form message cannot legally/technically be sent, Noxtill should show the appropriate template/approved route instead of allowing a send that will fail.
WhatsApp is a major Noxtill delivery layer. Intended workflows include:
- Nightly Close to the owner;
- booking confirmations;
- 24-hour and 2-hour reminders with one-tap reschedule where configured;
- digital receipts;
- neutral review requests;
- credit/udhaar reminders with balance and payment link;
- back-in-stock and aftercare messages;
- urgent low-rating/complaint alerts; and
- business reports for authorized owners/managers.
Marketing and operational usage should be measured separately for cost, quota and consent governance.
SMS and automated calls can be subject to consent, identification, do-not-call, quiet-hour and opt-out rules that vary by jurisdiction and message type. The business must configure its programs accordingly.
Noxtill should:
- process common opt-out keywords promptly;
- synchronize suppression across Marketing, CRM, Automations and Unified Inbox;
- prevent queued campaigns from sending after an opt-out where technically feasible;
- require appropriate consent evidence before high-risk automated marketing texts/calls; and
- preserve audit evidence for sender identity, purpose and opt-out handling.
Commercial email must use truthful routing and subject information, identify the sender as required, include a valid postal address where required and provide a functioning opt-out. Transactional/relationship messages should remain genuinely transactional.
In the U.S., CAN-SPAM applies to commercial email, including B2B commercial messages. In the UK/EEA and other jurisdictions, electronic marketing can require consent or another specific permission route. Noxtill should keep suppression records so an opted-out person is not silently re-added by an import, automation or AI agent.
For AI Phone Receptionist, call recording or transcription, Noxtill should provide configurable disclosure controls. A recommended opening pattern is:
“You’re speaking with an AI assistant for [Business Name]. This call may be recorded or transcribed where permitted.”
The customer must determine whether one-party or all-party consent, sector-specific recording rules, retention limits or voice/biometric restrictions apply. Noxtill should not assume one disclosure is legally sufficient everywhere.
Where a business enables fallback, Noxtill may try WhatsApp → SMS → email, but only if the person is eligible for the same purpose on the fallback channel.
A failed WhatsApp message is not permission to send marketing by SMS or email. The audit record should store provider result, fallback reason, consent check, chosen channel and final status.
Opt-out must be easy and honored at the correct scope. A person may opt out of marketing while still receiving necessary service communications. A global marketing suppression should block Marketing, Automations, CRM campaigns and AI agents from sending promotional communications.
No workflow or AI agent may override suppression merely because the contact is valuable or previously consented.
Review requests should be neutral. Noxtill should not default to sending review requests only to customers predicted to be positive if that creates deceptive review selection or violates a platform rule. Incentives must not be conditioned on positive sentiment where prohibited, and material connections must be disclosed.
Nightly Close is an operational owner summary, not end-customer marketing. It may include sales, profit, tomorrow’s bookings, outstanding credit and low-stock information. The business administrator controls destination, time, scope and role permissions. Sensitive financial details should not be sent to an unverified recipient.
Noxtill may pause or disable a channel, campaign, template, workflow or account where spam, complaint, consent or provider-policy risk becomes unacceptable. Severe violations can trigger suspension or termination under the AUP and Terms.