Direct Answer (TL;DR)
Brilo AI sets confirmation texts and emails to use a platform-managed sender name (for example, "Brilo Software") when a customer has not completed custom sender configuration or domain verification. This default protects deliverability and complies with carrier and email network requirements until your brand is verified. You can replace the platform sender with your brand once you provide and verify a sending domain or SMS sender ID and complete the setup steps in your onboarding workflow. Until those steps are finished, recipients may see the Brilo AI display name or a platform-managed phone number as the sender.
Why do my confirmation emails show Brilo Software? — When you haven’t finished custom sender setup or domain verification, Brilo AI uses a platform-managed display name and sending path to preserve delivery and compliance.
Why do my confirmation texts appear from a Brilo number instead of my brand? — Brilo AI will display a platform number or sender ID until you configure and verify your SMS sender ID for the target region.
How can I make confirmation messages show my company name instead of Brilo Software? — Complete domain verification for email and request a branded SMS sender ID following Brilo AI’s onboarding steps.
Why This Question Comes Up (problem context)
Buyers notice platform sender names during onboarding because email and SMS networks restrict who can claim a brand identity. Enterprises ask this question when confirmation messages go to customers but show the platform name instead of the company brand. This matters for customer trust, regulatory communications, and consistent brand experience in healthcare, banking, and insurance workflows.
How It Works (High-Level)
When you start using Brilo AI, confirmation texts and emails are routed through Brilo AI’s sending infrastructure by default. This preserves message deliverability while Brilo AI verifies that the sending domain or SMS sender ID belongs to your organization. Typical steps to switch from the platform sender to your brand include adding your sending domain, updating DNS records for verification (e.g., SPF/DKIM), and confirming an SMS sender ID where required. In Brilo AI, domain verification is a required step before Brilo AI will present your brand as the sender on outbound confirmations.
In Brilo AI, sender display name is the readable name recipients see in their inbox or message thread.
In Brilo AI, sending domain is the email domain you verify so Brilo AI can send on your behalf.
In Brilo AI, SMS sender ID is the phone number, short code, or alphanumeric label configured and authorized to represent your brand for text messages.
Guardrails & Boundaries
Brilo AI will not present your brand as the sender until the required verification checks are complete because doing so can harm deliverability and violate network policies. Brilo AI prevents unverified From addresses to reduce spoofing risks and protect recipient trust. Brilo AI also enforces message content and rate limits set during onboarding and by carriers; it will not bypass those controls to force branded delivery.
The default platform sender is the interim sending identity Brilo AI uses when customer verification is incomplete. This default may appear as “Brilo Software” or a platform-managed phone number. Brilo AI will not modify customer legal disclosures or opt-out mechanisms in confirmations without your approval; ensure any required legal text is included in templates you submit.
Applied Examples
Healthcare: A clinic using Brilo AI sends appointment confirmations. Until the clinic verifies its sending domain, patients may see the message come from the platform display name. The clinic should complete domain verification and ensure message templates avoid including protected health information in plain text unless the organization’s compliance process is in place.
Banking / Financial services: A bank triggers transaction confirmation emails. To preserve customer trust and avoid spam filtering, the bank verifies its sending domain so confirmations show the bank’s brand and use authenticated email headers.
Insurance: An insurer sends policy renewal texts. The insurer requests an SMS sender ID for the region and completes any carrier approvals so policyholders receive texts from the insurer’s brand name rather than a platform number.
Human Handoff & Escalation
When a confirmation message needs human review (for example, a delivery failure or a regulation-triggered escalation), Brilo AI workflows can flag the message and create a ticket or open a live-agent handoff. You can route escalations to your support queue, schedule a callback, or trigger an internal alert. Configure escalation rules in your Brilo AI workflow so that unverified-sender delivery failures create a staffed follow-up task.
Setup Requirements
Provide your sending domain (e.g., mail.yourcompany.com) so Brilo AI can begin verification.
Add or update DNS records (SPF/DKIM) as instructed by Brilo AI to complete email domain verification.
Confirm the desired From display name and email address for transactional confirmations.
Request an SMS sender ID or provisioning (phone number, short code, or alphanumeric sender) and supply any required legal or business information for carrier approval.
Submit final confirmation message templates, including any required legal text or opt-outs.
Test confirmations in a staging environment and verify deliverability and display name before going live.
Authorize Brilo AI to send on your behalf after you confirm verification is complete.
Business Outcomes
Improved customer trust: Branded confirmations increase recognition and reduce confusion for customers in regulated sectors.
Better deliverability: Verified sending domains and authorized SMS sender IDs reduce the chance of spam filtering or carrier blocking.
Clear auditability: Completing verification and template approvals creates a documented onboarding trail useful for compliance and internal audits.
FAQs
Why does the display name show 'Brilo Software' now?
Brilo AI uses a platform-managed display name by default until you complete sender verification steps; this protects deliverability and prevents sender spoofing.
How long does it take to switch to my brand name?
The timing depends on how quickly your team updates DNS records and whether an SMS sender ID requires carrier approval. Email domain verification is usually quick after DNS updates; SMS sender provisioning timelines vary by country and carrier.
Will my confirmation messages still be delivered while using the platform sender?
Yes. Brilo AI continues to deliver transactional confirmations using the platform sender to maintain service continuity; however, branded display and certain delivery characteristics require verification.
Can I change the "From" address or display name in the Brilo AI console?
You can request a display name and From address in Brilo AI, but the brand will only appear to recipients once Brilo AI verifies the sending domain or SMS sender ID according to onboarding requirements.
Do I need to worry about legal or compliance text in confirmations?
Yes. Include any mandatory disclosures, opt-outs, or regulatory language in your confirmation templates during setup. Brilo AI will not alter required legal content without your direction.
Next Step
Contact your Brilo AI onboarding specialist or account team to start domain verification and SMS sender provisioning.
Open a support ticket in the Brilo AI console requesting branded sender setup and attach the email templates you want to use.
Complete the DNS and template steps listed under Setup Requirements and run staged tests before enabling branded confirmations in production.