First setup checklist

Launch HoneyFalcon around one proven lead journey so the first production opportunity is routable, actionable, measurable, and easy to trace.

Why it matters

A dependency-aware setup prevents common gaps such as a live source with no eligible recipient, a timer that does not match working hours, or a CRM destination that has never seen an accepted test lead. Testing one controlled path first lets the team gain speed without introducing uncertainty.

See it in HoneyFalcon

Step 1 of 4: team and buffer checkpoint.

Step 2 of 4: allocation, capacity, and schedule checkpoint.

Step 3 of 4: synthetic lead intake checkpoint.

Step 4 of 4: connector and delivery-history checkpoint.

Set up in dependency order

1. Prepare the team

Open Team > Lead members and confirm which accounts and profiles are active.
Enable lead eligibility only for people who should receive automatic offers.
Set monthly targets and absolute limits to reflect the capacity you intend to route.
Invite any missing teammate and confirm that each person can sign in.
Choose one designated buffer when the company wants a specific terminal-rescue recipient.

2. Configure the routing policy

Choose Round robin or Broadcast in Lead routing > Allocation settings.
Set the concurrent pending capacity and the work-hour and off-hour acceptance windows.
Configure business hours and holidays before evaluating timer behavior.
Keep tag routing Off until tags, groups, source mappings, and agent assignments are complete; use Shadow before Enforce.

3. Set financial context

Set the company's standard lead cost.
Add agent-specific cost rules only where a deliberate percentage adjustment and lead count are needed.
Confirm the selected monthly period and counter behavior before using cost views for comparison.

4. Prove the manual journey

Create one synthetic manual lead.
Observe the offer, accept it, update the work record, and close with a test outcome.
Verify the expected usage, cost, and analytics records before enabling an automated source.

5. Connect production intake

Configure webhook or email intake only after the manual path is healthy. Validate the exact source contract and mappings with synthetic data before sending real customer enquiries.

6. Add outbound CRM delivery last

Create the connector from the correct provider preset or a verified custom contract.
Test the visible draft, save it, and activate the saved revision.
Accept a new synthetic lead and verify its independent delivery result in history.

A practical launch scenario

A three-person sales team can begin with one active recipient, Round robin, realistic business hours, a standard lead cost, and one synthetic manual lead. Once that route is predictable, the team can add the remaining members, observe tag routing in Shadow, and connect the first production source.

This sequence lets HoneyFalcon improve response speed from day one while every added rule has a visible purpose and a known result.

Change one layer at a time and retest the same synthetic journey. A controlled launch is faster than diagnosing several new routing, intake, and delivery rules at once.

You are ready for production when

At least one active, lead-eligible teammate can receive and accept the synthetic lead.
The selected allocation mode, response windows, business schedule, capacity, and optional tag policy behave as intended.
Accepted work appears in the expected usage, cost, and analytics views.
The chosen automated intake and any CRM connector have each been tested without confusing inbound capture with outbound delivery.