Direct Answer (TL;DR)
You can start outbound campaigns by uploading CSVs to Brilo AI when CSV-based contact import is enabled for your account, but a direct API integration is recommended for high-volume, real-time, and CRM-synced workflows. Brilo AI supports both contact list import (CSV upload) and programmatic campaign control via API or webhooks; CSV upload is best for one-off or batch campaigns, while API integration is better for automated scheduling, incremental syncs, and integrated call routing.
Can I start campaigns with a CSV?
Yes. You can upload a contact CSV to launch a batch outbound campaign in Brilo AI; this approach works for manual or scheduled batches.
Do I need an API to run outbound campaigns?
Not strictly. An API integration is optional but recommended for automation, CRM sync, and larger volumes.
Can I upload a CSV instead of building integration?
Yes for small-to-medium batches or pilot campaigns, but plan for API integration as volume, cadence, or data sensitivity grows.
Why This Question Comes Up (problem context)
Buyers ask whether CSV uploads are sufficient because teams want to understand operational trade-offs. Security, compliance, and reliability requirements matter more in regulated sectors like healthcare and banking. Enterprise teams also consider how contact data, real-time call results, and CRM records will be synchronized. Knowing whether Brilo AI requires an API or accepts CSVs helps procurement, security, and operations decide hosting, access controls, and integration timelines.
How It Works (High-Level)
Brilo AI supports two common workflows for outbound campaigns:
CSV upload (contact list import): upload a spreadsheet of contacts and campaign metadata, then configure call scripts, calling windows, and DNC suppression before launching a batch.
API integration (programmatic control): use Brilo AI’s API or webhook endpoints to create, update, and monitor campaigns, push incremental contacts, and receive call events for live CRM updates.
CSV upload is a manual contact import where you map columns (phone, name, consent flags) to campaign fields and schedule or launch immediately. API integration is a programmatic connection that automates contact sync, campaign creation, and event delivery to your systems. For CRM-connected workflows that require real-time logging or two-way sync, Brilo AI recommends integrating with your CRM via available connectors or the API; see the Brilo AI Salesforce integration for an example of CRM sync and logging.
Guardrails & Boundaries
Data validation and mapping: CSV uploads must match the required schema (phone formats, opt-in flags); malformed rows are rejected or quarantined.
Rate and volume controls: CSV batches may be subject to per-account throttles to avoid call spikes; very large lists typically require staged ingestion or API streaming.
Consent & suppression: Brilo AI expects consent flags and DNC suppression fields in CSVs and will honor suppression rules during dialing.
Error handling: CSV imports provide batch-level reports; they do not provide the same granular, per-record, real-time retry logic that an API workflow can surface.
Contact list import (CSV) is intended for batch dialing and is not designed for sub-second updates or event-driven syncs. Review Brilo AI’s campaign and answer-quality settings to configure safe dialing windows and escalation rules.
Applied Examples
Healthcare example
A care coordination team uploads a nightly CSV export from their scheduling system with patient phone, appointment time, and consent flag. Brilo AI handles call scripts, records attempted call outcomes, and produces a reconciliation report for the care team.
Banking / Financial services example
A collections team pilots a repayment outreach batch by uploading a secured-contact CSV with masked account IDs and explicit consent columns. For production, the bank moves to API integration to sync acknowledgements, update balances in the CRM, and enable near-real-time agent handoffs for urgent calls.
Insurance example
An insurance operations team uploads a claims outreach CSV for policyholders affected by an outage. Brilo AI runs the batch, logs outcomes, and flags calls that require human follow-up based on keywords or caller responses.
Human Handoff & Escalation
Brilo AI supports human handoff from both CSV and API-driven campaigns:
When a caller requests a human or triggers a defined escalation intent, Brilo AI can transfer the call to an on-duty agent, open a ticket, or place the caller in a callback queue.
For CSV-originated campaigns, escalation actions are defined in the campaign configuration (routing rules, callback windows, and agent groups).
For API-driven workflows, Brilo AI can emit an event webhook on handoff conditions so your systems can immediately notify the right agent or open a CRM case.
Buyers commonly use CSV uploads for batches and configure escalation thresholds in the campaign settings; for instant agent notifications and availability checks, an API integration provides tighter control.
Setup Requirements
Prepare: Standardize your contact list with required columns (phone number, name, consent/DNC flags, any custom fields).
Validate: Ensure phone formatting and opt-in indicators match Brilo AI’s import schema and pre-check for duplicates.
Upload: Log into Brilo AI and use the contact import UI to upload the CSV and map columns to campaign fields.
Configure: Define calling windows, call script, suppression lists, escalation rules, and retry logic in the campaign settings.
Test: Launch a small test segment to confirm mapping, call flow, and handoff behavior before scaling.
Integrate (optional): Connect your CRM or implement Brilo AI’s API/webhook flows to move to programmatic contact pushes for continuous sync or automated logging.
If you use a CRM connector like Salesforce or HubSpot, Brilo AI can align contact records and push call activity—review your CRM connector setup before switching from CSV to API-based sync. For integration details, see Brilo AI HubSpot integration overview and Brilo AI Salesforce integration overview.
Business Outcomes
Faster pilots: CSV uploads let you launch pilot outbound campaigns without engineering time, enabling quick validation of scripts and call flows.
Lower operational lift for occasional batches: Teams with periodic outreach avoid building an API pipeline.
Better automation at scale: API integration reduces manual work, prevents duplicate uploads, and provides near-real-time CRM updates and analytics for compliance and reconciliation.
Safer operations: Using Brilo AI’s suppression and consent fields reduces compliance risk when CSVs are validated and managed correctly.
FAQs
Can I include consent and DNC fields in a CSV?
Yes. Brilo AI accepts consent and suppression columns as part of the CSV import schema. Include explicit opt-in flags and DNC markers to ensure Brilo AI honors suppression during dialing.
What size CSV can I upload?
Upload limits and recommended batch sizes depend on your Brilo AI account plan and dialing policies. For very large lists, Brilo AI recommends staged uploads or switching to an API ingestion approach to avoid throttling.
Will call results sync back to my CRM after a CSV campaign?
Call outcomes from CSV campaigns can be exported and manually imported, or automatically synced if you use a CRM connector or the Brilo AI API to push results into your CRM.
Do CSV uploads support incremental updates?
CSV uploads are typically full or partial batch imports; incremental, record-level updates are best handled through the API so you can upsert contacts and avoid duplicate processing.
Is there a template for the CSV?
Brilo AI provides a required import schema (phone, name, consent flags, custom fields). Follow the import UI mapping and run a small test segment to verify field alignment.
Next Step
Review Brilo AI’s Salesforce integration for CRM sync and campaign logging.
Review Brilo AI’s HubSpot integration for CRM connector options and contact sync guidance.
If you’d like help choosing the right path, contact your Brilo AI account team to review expected volumes, compliance requirements, and recommended ingestion workflows.