Skip to main content

How do I import a customer contact list into Brilo AI?

Y
Written by Yatheendra Brahmadevera
Updated over a week ago

Direct Answer (TL;DR)

Brilo AI Customer List Import lets you upload a contact file (typically CSV) and map columns so Brilo AI voice agents can recognize and personalize calls. The process validates fields, applies deduplication rules when enabled, and can update or create records in your target system when you connect your CRM or webhook endpoint. You can configure field mapping, suppression flags, and consent indicators during import so Brilo AI respects opt-outs and routing rules. For large lists, Brilo AI can process the import asynchronously and report back on errors and skipped rows.

How do I upload contacts to Brilo AI? — You can upload a CSV and map columns; Brilo AI will validate and import the records, reporting any errors.

Can Brilo AI deduplicate my contacts during import? — When enabled, Brilo AI applies configured deduplication rules to prevent duplicate outbound attempts.

How do I keep my CRM and Brilo AI in sync? — Connect your CRM or webhook endpoint and configure upsert/match keys so Brilo AI updates existing records instead of creating duplicates.

Why This Question Comes Up (problem context)

Buyers want to know how to get existing customer data into Brilo AI quickly and safely. Enterprises need predictable field mapping, data validation, and governance controls before letting an AI voice agent call or message customers. Regulatory and operational teams also want clear behavior for suppression lists, consent flags, and record matching to avoid compliance violations and costly mistakes. Understanding import behavior reduces implementation time and prevents downstream call failures.

How It Works (High-Level)

Brilo AI Customer List Import accepts a contact file (CSV) or an automated feed and converts it into the agent’s contact store according to the mapping rules you supply. During import, Brilo AI validates required fields (for example, phone number format), applies deduplication and suppression policies, and optionally triggers webhook callbacks for rows that need manual review.

A customer list is the dataset of contacts and structured fields that Brilo AI uses to personalize outbound and inbound call routing.

Contact mapping is the configuration that links CSV columns (for example, phone, first_name, policy_number) to Brilo AI contact fields.

Brilo AI can be configured to perform imports synchronously for small batches or asynchronously for larger lists; asynchronous imports return a job report with counts of successes, failures, and skipped rows.

Related product reading: Brilo AI customer support overview

Guardrails & Boundaries

Brilo AI enforces several stop-gates during import to protect operations and privacy. File parsing failures, invalid phone numbers, or missing required fields cause rows to be rejected with an error report. Brilo AI will not place calls to contacts on a configured suppression list or contacts marked with an opt-out flag during import. Large imports can be rate-limited to avoid sudden spikes in outbound activity.

Suppression list refers to the configured set of contacts or flags that prevent outbound engagement for legal or operational reasons.

Do not use the import to bypass consent controls: Brilo AI will honor opt-out and suppression fields if those fields are mapped during import. See your organization’s data retention and answer quality rules before enabling automatic outbound workflows.

Applied Examples

  • Healthcare: A clinic uploads a patient outreach list with fields for phone, appointment_date, and consent_flag. Brilo AI validates phone formats and skips rows where consent_flag = false, then places appointment reminder calls only for valid, consented contacts.

  • Banking: A bank imports a list of overdue-account contacts with account_id, balance, and contact_preference. Brilo AI maps account_id to the agent context and uses contact_preference to choose voice or SMS follow-up, while deduplicating contacts that appear across multiple portfolios.

  • Insurance: An insurer uploads policyholder contacts with suppression flags to prevent outreach for policies marked as under-dispute; Brilo AI rejects those rows from outbound campaigns and includes the rejection reason in the job report.

Human Handoff & Escalation

When Brilo AI identifies rows during import that require human review (for example, invalid contact data or duplicate resolution conflicts), it can mark those records and surface them in the import job report. When configured, Brilo AI workflows can escalate a contact to a human agent by triggering a handoff route or creating a task in your CRM via webhook. You can also configure thresholds (for example, percent error or number of rejects) that pause automatic campaign start until a human approves the imported list.

Setup Requirements

  1. Prepare a CSV file with consistent column headers (for example: phone, first_name, last_name, consent_flag).

  2. Validate phone numbers and required fields before upload to minimize rejects.

  3. Map CSV columns to Brilo AI contact fields in the import UI or API.

  4. Choose import behavior: create-only, upsert (match by a key), or update-only.

  5. Configure suppression and consent column mapping so Brilo AI will honor opt-outs.

  6. Connect your CRM or webhook endpoint if you want Brilo AI to upsert records or emit row-level callbacks.

  7. Review the import job report and resolve any flagged rows before launching outbound workflows.

Optional reading that relates to import planning: Brilo AI customer engagement resources

Business Outcomes

  • Faster onboarding of existing customer bases so Brilo AI voice agents can begin personalized outreach.

  • Reduced manual cleanup work because Brilo AI reports errors and supports deduplication and validation during import.

  • Safer outreach by enforcing suppression and consent flags at import time to lower operational risk.

These outcomes reduce time-to-value while keeping control with your operations and compliance teams.

FAQs

What file formats does Brilo AI accept?

Brilo AI accepts CSV files for customer list import. If you need a different format, export to CSV first or contact your implementation lead for alternatives.

Can I update existing contacts rather than creating duplicates?

Yes. Configure the import to use upsert behavior and specify a match key (for example, customer_id or phone). Brilo AI will attempt to match and update existing records when the match key is provided.

How does Brilo AI handle duplicates?

Brilo AI applies configured deduplication rules during import. You can choose whether to keep the first match, the most recent, or flag duplicates for review depending on your operational policy.

Will Brilo AI call contacts who opted out?

No. If your import maps an opt-out or suppression field, Brilo AI will respect that and exclude those contacts from outbound workflows.

What happens if the import fails for many rows?

Brilo AI provides an import job report listing errors and rejected rows. You can correct the source file and re-run the import. For large failure rates, Brilo AI can pause automated campaigns until an administrator approves a retry.

Next Step

If you’re ready to import: prepare a sample CSV and contact your Brilo AI implementation manager to schedule a test import. If you need help mapping fields or setting up suppression rules, open a support ticket through your Brilo AI onboarding channel.

Did this answer your question?