Contacts & Data Collection

Keep caller details ready for the next conversation.

Your receptionist collects the details your Canadian service business needs. Keep messages and prior calls with the contact so your team can respond with context.

People and companies

See the person, the company, and the history behind the call.

Dialbox connects contacts to company groups, preferred channels, appointment history, call summaries and SMS replies. Your AI receptionist can greet returning callers with context while your team sees the same customer story in one place.

People and companies view

Group contacts by company name or business email domain so account history stays connected across every caller.

Duplicate contact cleanup

Merge duplicate records and keep prior calls, texts, appointments, and notes tied to the right customer.

Preferred contact method

Keep contact preferences with the inquiry so your team can handle the next inbound conversation with context.

Company reception history

Review reception requests from contacts at the same company while keeping each caller’s context connected.

The Problem

Give your team a useful reception record.

Scattered caller notes

  • Prior calls are hard to find
  • Freeform notes like "yeah I guess next Tuesday works"
  • You sort through "yep," "sure," and "absolutely" manually
  • Caller details need to be copied between tools
  • Messages lack the service details staff need

Dialbox

  • "Hi Sarah, I see you're a Gold member"
  • Structured fields: date: Tuesday, confirmed: yes
  • Configured aliases map common responses
  • Data stays connected to your reception records
  • SMS replies grounded in the caller’s request
Intelligent Response Matching

Collect caller answers in consistent fields.

People don't talk in database fields. They say "yeah," "I've been coming here for years," and "just a trim." Dialbox understands what they mean and records structured values your systems can actually use.

Alias matching handles variations

"Yeah," "yep," "sure," and "absolutely" all become yes. Define once, apply everywhere.

Context-aware extraction

"I've been coming here for years" becomes existing_customer. Configure the field values your team needs for reception.

Multiple values from one response

"Yeah, right away please" captures both yes and urgent in their respective fields.

Preserves unknowns

Unexpected responses keep their original text. Review them later and add new aliases if needed.

Example configured field identifiers

Alias Matching
"Yeah, right away please"
yesurgent
"I've been coming here for years"
existing
"Just a trim"
haircut
"Nope, not interested"
no
Contact Recognition

Keep returning caller context available

Import your customer list and keep reception records with the matching contact. Your team can review prior messages and calls before responding.

Import up to 10,000 contacts

Upload a CSV, map your columns, and your customer list is ready. Validation catches bad phone numbers and emails.

Personalized returning caller greetings

"Welcome back, Sarah. You last called on March 10th." Use [Caller First Name] and [Last Call Date] tags so returning callers feel recognized, not processed.

Custom fields for any data

VIP status, service preferences, policy numbers, membership tiers. Track what matters to your business.

Complete conversation history

Every call, message, and appointment linked to the contact. See what was discussed and what actions were taken.

Language preference on every contact

Dialbox detects each caller's language and saves it to their contact record automatically. Future calls use their preferred language, voice, and greeting. Check the saved language preference in the contact record.

Contact matched
0:03
SJ
Sarah Johnson
VIP(416) 555-0142
Member2022
PlanGold
Calls12
Appointment rescheduled2 days ago
Confirmation SMS sent2 days ago
Invoice inquiry1 week ago
"Welcome back, Sarah. You last called on March 10th."

Ready to stop cleaning up data manually?

Reusable Fields

Define once. Use everywhere.

Create a custom field with its options, aliases, and output labels one time. Use it across message taking, connected-calendar booking, and Playbooks. Update in one place, changes apply everywhere.

Pre-built templates

Yes/No/Maybe, Urgency Level, New/Existing Customer. Common fields with aliases already configured.

Choice questions for voice

"Are you interested in haircut, colouring, or styling?" Works even when callers say "color job" or "just a trim."

Custom output labels

Send "Policy #" to your Google Sheet instead of "policyNumber." Match your existing column names.

Example configured field identifiers

Field Templates3 active

Yes/No/Maybe

Choice
yesnomaybe

"yeah," "nope," "let me think"

Urgency Level

Choice
urgentnormallow

"ASAP," "whenever," "no rush"

Customer Type

Choice
newexisting

"first time," "been here before"

Data Integration

Clean data lands exactly where you need it

Share caller details through supported integrations or configured webhooks. Use field mappings and aliases to keep the information consistent.

Direct CRM sync

Send reception details to a supported CRM or a configured webhook endpoint. Available fields and actions depend on your connection.

Google Sheets integration

Map reception fields to your spreadsheet columns through the supported Google Sheets connection.

Reception details

Keep the reason for each inquiry alongside the contact so your team can respond accurately.

Normalized everywhere

Same clear reception details in your CRM and your sheets. Review your field mappings during setup.

POSTyour-crm.com/api/contacts
{
"name":"Sarah Johnson",
"interested":"yes",
"urgency":"high",
"service":"haircut",
"customer_type":"existing"
}
200 OKAll fields normalized
FAQ

Common questions

How does alias matching work?

When a caller says 'yeah', 'yep', or 'sure', the system automatically normalizes these to 'yes' based on your configured aliases. You define the mappings once, and AI applies them consistently across all calls. Review collected details alongside the call record.

Can I import my existing customer list?

Yes. Upload a CSV with up to 10,000 contacts at once. Map your columns to Dialbox fields during import. Choose how to handle duplicates: skip them, update existing records, or create new ones.

How do custom fields appear in webhooks?

You control the output labels. If your Google Sheet expects 'Policy #' but your field is named 'policyNumber', set the output label to match. Data flows to your systems in exactly the format they expect.

What happens if data doesn't match any alias?

The original response is preserved. If a caller says something unexpected, you get their exact words rather than an incorrect match. You can review these and add new aliases to improve future matching.

Can I use collected details when replying to a contact?

Yes. Details collected during reception stay with the contact so your team can understand the inquiry and reply by SMS with context.

How many custom fields can I create?

Custom-field availability depends on your plan. Check the options in your account or ask our team about the fields your reception workflow needs.

Can I delete or export contacts in bulk?

Yes. Select multiple contacts with checkboxes or use the select-all toggle. Bulk delete includes a confirmation dialog so nothing gets removed by accident. Export selected contacts to CSV with a progress indicator. Dismissible filter chips make it easy to narrow down your selection first.

Ready for AI reception?

Start capturing
clean data

Import your contacts and choose the details to collect during reception. Test your setup before forwarding customer calls.

New Lead - Alex Morgan

(416) 555-0189 · 2 min call

Qualified

AI Summary

Caller wants pricing, has questions about setup, and asked to book a consultation later this week.

Urgency

High

Sentiment

Positive

Action

Message captured

Privacy controls for receptionTest before forwarding calls7-day free trial. Credit card requiredMonth-to-month, cancel anytime