Frequently asked questionsQuestions,
answered.
How Hawfinch keeps your data separate, how quickly leads move, how it connects to your suppliers and buyers, and who answers when you need help.
Is my data kept separate from other customers?
Yes. Every request is scoped to your account, so other customers can never see your leads, campaigns or buyers. If you need your own servers and database, for example for compliance, dedicated infrastructure is available on Enterprise.
How fast is "real-time" ingestion?
Your supplier gets a response as soon as the lead is accepted. Routing starts straight away in the background, so how quickly a lead reaches a buyer mostly depends on how fast that buyer's system responds.
Can we bring our own integrations?
Yes. Suppliers post leads to a REST API, and a buyer can be any HTTP endpoint, by direct post or ping post, with field mapping, static fields, body templates and headers per buyer. Everything in the dashboard is available through the REST API too.
What's the support model?
Every plan includes 24/7 support from our UK-based team, including weekends and bank holidays. You reach engineers who know your account, your campaigns and your buyer setup, rather than a generic ticket queue. Enterprise plans add a named contact and a contracted SLA.
How do you handle data residency?
All data is stored in London, in the United Kingdom, and Hawfinch supports your obligations under UK GDPR. If you need single-tenant infrastructure, it is available on Enterprise.
By topic
More answers on each product page.
- Lead managementIntake, checks, dedupe and suppression.
- CampaignsDelivery groups, buyers, caps and filters.
- AnalyticsReports, revenue and buyer performance.
- PricingPlans, lead allowances and what is included.
- EmailThe email builder, automations and the never-email list.
- AssistantWhat it can see, and how it answers why a lead went where it did.
- Compare platformsHow Hawfinch compares with other lead platforms.
- Something else?Ask our UK team. We answer 24/7.