--- title: "How should we automate sales follow-up across WhatsApp and Teams?" description: "A practical workflow for LATAM sales teams that need timely WhatsApp follow-up, internal Teams approvals, and a reliable CRM record." author: "Carlos García" published: 2026-09-06 updated: 2026-09-06 language: en human_url: "https://kiia.cloud/blog/automate-sales-follow-up-whatsapp-teams/" --- > **In 60 seconds:** Use the CRM as the source of truth, not WhatsApp or Teams. A scheduled flow finds opportunities that need attention, checks consent and message eligibility, drafts the next approved message, and asks for human approval only when there is a real exception. The WhatsApp Business channel sends it. The flow writes the outcome back to the CRM and alerts the owner in Teams. Start with one follow-up moment, one segment, and explicit stop rules. Do not automate from a salesperson's personal WhatsApp account. A sales manager usually asks this question after seeing the same pattern: good leads go quiet, reminders live in personal calendars, and nobody knows whether the last message was sent. The answer is not a bot that talks to every prospect. It is a small operating system for follow-up. ## A decision framework before choosing tools Score the proposed flow on five questions: 1. Is there one system that reliably says who the contact is, who owns the opportunity, and what happened last? 2. Does the business have permission and a valid reason to contact this person on WhatsApp? 3. Can the team define the next action without reading the salesperson's mind? 4. Which messages are safe as approved templates, and which need review? 5. What event must stop automation immediately? If the CRM data is incomplete, fix that first. Automating an unreliable stage field only sends the wrong message faster. If the decision depends on negotiation context, let the flow prepare work for a person instead of sending autonomously. This same test helps when deciding [what to automate first](/blog/what-to-automate-first-in-a-business/). Choose a repeatable bottleneck with a clear owner and visible outcome. ## A concrete WhatsApp and Teams workflow Start with a single case: a qualified opportunity has had no recorded activity for two business days. 1. A scheduled Power Automate flow reads eligible opportunities from the CRM. 2. It excludes records with no consent, closed opportunities, recent replies, active disputes, or a manual hold. 3. It selects an approved message template using language, stage, and next action. It does not invent an offer or delivery date. 4. If the message contains a nonstandard discount, commitment, or attachment, the flow posts an approval card in Teams to the opportunity owner or manager. 5. The WhatsApp Business provider sends the approved template. 6. The integration records the template ID, timestamp, provider status, and responsible owner in the CRM. 7. A reply closes the sequence, creates a task, and alerts the owner in Teams. 8. Delivery failure or missing data goes to an exception queue rather than disappearing in a flow log. Power Automate has WhatsApp options, including an [Independent Publisher connector in preview](https://learn.microsoft.com/en-us/connectors/whatsappip/) and the [tyntec WhatsApp Business connector](https://learn.microsoft.com/en-us/connectors/tyntecwa/). Availability, licensing, support, and regional fit must be checked for the selected tenant. Preview is a reason to test carefully, not a production guarantee. Meta's Cloud API also has requirements for [business phone numbers](https://developers.facebook.com/docs/whatsapp/cloud-api/phone-numbers). Treat number registration and business verification as project work. A personal number and the consumer app are not a sound integration boundary. ## Where Teams belongs Teams is the staff interface, not the sales database. Use it for alerts, exception approvals, and links back to the opportunity. Avoid making a channel thread the only record of a decision. Approve only decisions where review changes risk. Examples include a special commercial term, a message after a complaint, or a promise that affects operations. If every routine reminder waits for approval, the team recreates the original delay in a different screen. Microsoft documents [flow limits and approval behavior](https://learn.microsoft.com/en-us/power-automate/limits-and-config). Long waits need special care. Keep durable business state in the CRM or Dataverse and design a separate resume mechanism rather than expecting one flow run to wait indefinitely. ## Pilot checklist Before launch, confirm: - one opportunity owner and one CRM stage vocabulary - consent or another reviewed contact basis for each target segment - approved message templates in the correct local Spanish or English - business hours and country time zones - stop events for replies, opt-outs, closure, disputes, and manual holds - a retry limit plus an exception owner - a dashboard for eligible, sent, delivered, replied, stopped, and failed records - access controls for CRM, Teams, Power Automate, and the provider Run the pilot with a narrow segment. Review failed and stopped records daily. The useful metric is not message volume. It is whether the next legitimate sales action happens on time and remains visible. ## Limits to make explicit WhatsApp templates, categories, and charges can change, so verify current rules with Meta and the provider rather than embedding a price in the business case. A connector does not solve consent, data quality, or sales ownership. AI can draft wording, but it should not create facts, discounts, stock promises, or legal claims. Also plan for channel outages and throttling. The fallback can be a CRM task or email to the owner. It should not be uncontrolled repeat sending. ## What Kiia would build first At Kiia, we would map one follow-up state from trigger to reply, test the connector and number setup, and implement the audit trail before adding AI drafting. That creates a useful slice that sales and operations can inspect. Once it behaves well, the same foundation can support collections or an [ERP-connected management assistant](/blog/ai-executive-assistant-erp-sales-collections/) without turning Teams into another silo. ## Frequently asked questions ### Can Power Automate send WhatsApp messages from a personal account? No. A production workflow needs a WhatsApp Business setup and a supported provider or connector. Do not build it around an employee's consumer app. ### Should every follow-up require approval in Teams? No. Approve exceptions such as unusual discounts or sensitive wording. Routine, preapproved reminders should run automatically with clear stop rules. ### What should happen when a prospect replies? Stop the automated sequence, assign an owner, save the reply context in the CRM, and notify the right salesperson.