Check that your CRM was set up correctly: the final tests

Milestone 8 of 8 · The implementation closed

When you finish you'll have: the certainty that a stranger can contact you today and get all the way to your report without anyone pushing them by hand.

You'll need a phone number and an email address that do not exist in your database, and a stretch of time without interruptions.

The end-to-end test

A single lead going through everything, in order. If it breaks, the stretch where it broke tells you which piece is missing.

Choose the channel people really contact you through. If it's WhatsApp, send a message from that phone to your connected number. If it's your site, submit the form from the published site, not from the editor.

Stretch 1 — It comes in and becomes something

• The inquiry shows up in the CRM: the conversation in CRM > WhatsApp, or your form's submission.
• A prospect or a deal was created, according to the destination you configured. Seeing the conversation isn't enough: if no entity was created, there's nothing to assign, alert about or work.
• It carries its origin, and the custom fields you mapped came in with data.

Stretch 2 — Someone takes charge

• It has an assigned owner.
• That owner got the email alert.
• In CRM > Prospects that lead shows its Next action mark: Not contacted while nobody touches it, Waiting on you if they wrote and there's still no reply.

Stretch 3 — It can be worked and it can be closed

• You can reply from the CRM and the message reaches them.
• You send a template to a contact you haven't talked to in more than twenty-four hours and it sends without error. This is the one that fails if you didn't load a payment method in your WhatsApp Business account at Meta. Receiving works just the same, so it's perfectly possible to have gotten this far believing everything was ready.
• The email a salesperson with a connected mailbox sends to a CRM contact shows up on its own in that deal's history.
• If you activated an AI position on that line: it replied, the reply sounds like your company and it became the owner.
• You convert it into a deal, move it through a stage and mark it won.

Stretch 4 — On the lead's side

This is the stretch almost nobody runs, and the only one that looks at the other end. With the same test lead:

• If it came in through a form, that address received something. A confirmation, not silence. If nothing arrived, your auto-reply is off or you're missing the verified domain.
• Time the first reply. From when you sent the inquiry until the first message went out to that person, how long passed? That number is what your lead experiences, and it's the only piece of data in the whole implementation they notice.
• If you booked a test meeting, the confirmation arrived — and, with reminders on, the advance notice arrives too.
• Read what you received as if you weren't you: is it clear who's writing, from which company, and what happens next?

The attribution test

Visit your site through an address that carries your campaign parameters and, from there, generate an inquiry.

• The lead shows its campaign of origin, not as direct traffic.

If it shows as direct, the pixel is missing on that page or the parameters are missing from the ad. Check the installation from Settings > Tracking; the steps are in Connect forms and ads, and know which campaign each lead came from.

The reports test

Go to CRM > Performance.

• Historical won deals appear in their real month, not in the month you imported them.
• You can cross by source and by salesperson.
• Your Deals custom fields appear for grouping reports, with the · Personalizado suffix (long-text and file fields aren't useful for grouping, so they aren't offered).
• The amounts are in your currency.
• In Forecast, the Weighted value isn't zero. If it's zero, your open deals have no value loaded, and the probabilities you configured in milestone 3 aren't doing anything.

If everything shows in dollars, the pipeline's default currency was set wrong. If your history shows mixed with the leads your team enters by hand, it was imported with the system's Manual source instead of a source of your own. See CRM reports: ready-made sales reports and building your own.

What if something fails?

Almost every failure is explained by one of these six missing pieces. Look for them in this order:

• The WhatsApp line isn't added → no message comes in, and they get lost. See Connect WhatsApp to the CRM: number, line and source.
• The lead source doesn't exist or isn't tied to that channel → you see the conversation or the form's email arrives, but nothing gets created. See Connect forms and ads, and know which campaign each lead came from.
• The assignment rule doesn't match → the lead comes in with no owner and no alert. See Distribute leads and get your team operating the CRM every day.
• The payment method at Meta isn't loaded → you receive, but no message goes out.
• The email domain isn't verified → your lead doesn't get your form's confirmation, and your emails go out from an address that isn't your company's. See Configure your sending domain so your emails arrive.
• The currency or the attribution source were set wrong in the historical load → reports don't add up and can't be crossed by origin. See Prepare and verify loading your historical base into the CRM.

The symptoms in more detail are in Leads don't come into the CRM or don't sync and My WhatsApp doesn't send or receive messages.

What's next?

The configuration is done. What decides whether the CRM is useful or turns into a dead database starts now: Sustain the CRM for the first 30 days so your team really uses it.

Before closing, write down the number from stretch 4: how long you took to give the first reply. It's the baseline you'll compare against on day 30.