Яндекс.Метрика

How do you get website leads straight into your team chat?

Your website form sends the lead to a bot, the bot posts a card in the sales channel, a rep clicks Claim, and the lead is theirs. The customer hears back in minutes, not the next day by email. Walk through the lead’s path yourself below.

kuhni-moscow.ru/zayavka
Custom kitchens · Moscow

Your dream kitchen in 21 days

Free measuring and a 3D design. Leave a request and a manager will call you back within 15 minutes during business hours.

1,200+kitchens installed4.9rating on Yandex Maps

Get a quote

By clicking the button, you agree to our privacy policy

Fill out the form as a customer and click "Send request."

Why handle leads in your team chat

Email and personal messaging apps hold up while you get five leads a day. Past that, customers start slipping through the cracks.

  • Everything in one place. The lead, the discussion and the decision sit right next to your other work chats. No need to keep email, your CRM and a personal messaging app open.
  • Reply in minutes. The notification arrives where your team already works, not in an inbox someone checks once an hour. You reply before the customer has time to try a competitor.
  • Stay focused. Each lead lives in its own thread, so the main chat isn’t cluttered. Notifications are up to you: whoever’s on call gets everything, everyone else gets only mentions.
  • Nothing gets lost. Lead history stays with the company, not in a rep’s Telegram. When someone leaves, you turn off their access, and the conversations and customers stay.
  • Managers see the big picture. Who took which lead, how many are in progress and where things are stuck: it’s all visible from threads and reactions, no reports or status meetings needed.
  • Grows with you. Today it’s a card from a bot. Tomorrow it’s a Claim button, a CRM integration and an AI agent that answers common questions.

How to set it up

20 minutes, no developer needed. You'll need administrator rights in Pachca.

In Pachca

  1. 1

    Create a "Leads" chat

    + next to search Chat. Add your sales managers.
  2. 2

    Create a bot

    Automations Integrations Webhook +. Name it "Website," keep the Public toggle off and leave everything else as is.
  3. 3

    Copy the Webhook URL and paste the template

    On the Incoming webhook tab copy the Webhook URL. Below it, select Mustache and paste this into the template field:
    **New website lead**
    Name: {{name}}
    Phone: {{phone}}
    Comment: {{comment}}
    The names in curly braces must match your form fields. How to find field names.
  4. 4

    Add the bot to the chat

    Chat settings Add members the Integrations tab Website. Only an admin or the chat's creator can do this.

On your website

Pick one of three options, depending on your setup.

  1. A

    A form on Tilda, Bitrix24, amoCRM or another website builder

    Find Webhook in the form settings, paste the URL from step 3 and set the data format to JSON. Send a test request from your site: a message from the bot will show up in the chat.
  2. B

    Your form doesn't support webhooks, or leads live in a CRM

    Connect through Albato: set up a "new lead" "message to Pachca" flow, no code, 250 services. You don't need the template from step 3, since Albato builds the message text.
  3. C

    A custom website, and you have a developer

    Give this skill to Claude, ChatGPT or Cursor. It covers the API endpoints, the JSON format, "Claim" buttons, click handling and where to host the handler. The assistant will ask about your stack and write the code.

In your team

  1. 5

    Agree on who claims each lead

    Whoever's on call reacts with ✅ and replies in the thread. All communication about the lead stays in the thread. Target response time: 15 minutes during business hours.

The "Claim" button from the demo is built with the API. The skill above covers it. To set it up by hand, see bot buttons and an example of handling clicks in n8n.

Troubleshooting

  • No message: the bot isn't in the chat or the template is empty.
  • Curly braces instead of data: the field names in the template don't match the form.
  • The form sends form-data, not JSON: connect it through Albato.