Default fields
Name, email, phone, company, website, industry, country, state, address, postal code, location, tags, imported dates, and safety status are treated as first-class contact data.
Contact database
Contacts are neutral reusable prospect records. They should not contain campaign reply state, CRM status, or outreach history.
Required manual fields
Manual contact creation requires name, email, company, and industry. Other fields are optional.
Imports and smart matching
- Supported import formats include manual entry, CSV, Excel, and JSON.
- Fast import stores contacts quickly. Safe import queues contacts for deliverability checks in the background.
- Uploaded columns are matched to known fields even when users use different labels.
- Unknown columns are preserved as contact-specific extra fields.
- Extra fields are visible when viewing the contact but do not pollute the default contact model.
Search, filters, and actions
- Search supports names, email, company, industry, location, country, and other stored values.
- Filters support date ranges and contact attributes.
- Users can edit, delete, bulk select, and smart-delete selected contacts.
- Long table values should truncate visually and open in a polished centered view modal when needed.
- Large accounts load contacts in batches so the UI stays fast even with large prospect databases.
Safe import checks
- Valid format, domain existence, MX records, disposable domains, role-based addresses, catch-all behavior, and SMTP handshake results contribute to contact safety.
- Safe means the evidence is strong enough for outreach. Risky means the domain looks usable but the mailbox is not explicitly confirmed. Invalid contacts should be filtered out of campaigns.
- Campaign creation can filter contacts by the safety level the user is willing to send to.