İçeriğe geç
Peak Atlas

Peak Automations / Lead routing

The lead is in.Who takes care of it now?

Leads that reach everyone end up belonging to no one. With Peak Automations an AI step assigns every new contact or form enquiry to one of your topics. For each topic a small automation of its own creates a task for the responsible person and posts in the matching Slack channel.

Put the goal into words. Add perspectives and timing right below.

Local draft · no product activation
See the routing flow

Try it on a local sample lead.

One lead. The right person. No forwarding.

Lead / topic / owner

01When02Only if03Then
Working example / routing

Who gets which lead.

When
A contact is created in the CRM
Only if
The AI picks the topic “consulting”
Then
Task for consulting, message in #consulting
Editorial structure sketch · not the product interface

Your routing rule

From three answers to clear ownership.

Fill in the example with a made-up lead and see how trigger, criterion and hand-over fit together. Nothing is connected or sent.

Local working example · nothing is saved or sent. Please don't enter personal data.

Peak Automations / Start noteLOCAL DRAFT
01 / Your thoughts
02 / Your start noteLocal preview

Three questions. A lead with an owner.

Draft · not yet put together

The trigger
Still open
The criterion
Still open
The hand-over
Still open
Your input appears here right away. With “View the start note” you check the three details locally.

From intake to ownership

One topic. One person. One channel.

The order makes sure every lead lands exactly once with exactly one person.

  1. 01Case

    The trigger arrives.

    When

    A contact is created in the CRM

    A new CRM contact, a submitted form, a Calendly booking or a new HubSpot contact starts the run. Duplicate events are recognised and processed only once.

    Event → one run
  2. 02Action

    The topic decides the path.

    Only if

    The AI picks the topic “consulting”

    The AI step picks exactly one topic from your list. Because an automation doesn't branch today, there is one automation per topic with its own condition.

    Topic → matching automation
  3. 03Result

    The person knows.

    Then

    Task for consulting, message in #consulting

    A task in Peak Task, a note in the Inbox, a message in the channel. In the local example you get a routing note.

    Sample artifact → routing note

The next proof is the product

Create your first routing automation.

Describe it in one sentence, let Peak ask its questions and start the test run. The conflict check shows when two automations would handle the same lead.

Start Peak Automations

Peak Automations / Your next step

No lead without a name next to it.

Try the example with the topic where it's most often unclear today who is responsible.

See the routing flow
Local working example

Every lead has a name next to it.

Task for consulting, message in #consulting

Frequently asked questions

Can one automation distribute leads to several teams?

Not within a single automation today. You create one automation per topic with its own condition; the conflict check shows overlaps.

Is there round-robin distribution?

No, even round-robin distribution is not available yet. Ownership follows the criterion you set.

Which channels can Peak use?

Tasks in Peak Task, notes in the Peak Inbox and messages in Slack through your workspace's connection.

More in Peak Automations