Skip to main content

WhatsApp components

Components (/whatsapp-business/components) are reusable message building blocks—headers, bodies, buttons, lists—referenced by Conversation Builder and related WhatsApp automations. Centralizing components keeps brand voice consistent and reduces rework when Meta updates template structure.

Video

Video coming soon for this topic

Who can do this​

WhatsApp Business users with builder permission.

Before you begin​

What you'll accomplish​

  • Component library created
  • Components referenced in a published conversation path

Step-by-step procedure​

Manage components​

  1. Sidebar → Marketing → WhatsApp → Components.
  2. Select Create (or equivalent new-component action).
  3. Define component type (text, media, button set, list, etc. per UI).
  4. Add labels and payload fields required by Meta.
  5. Save—component appears in library list.

Use in Conversation Builder​

  1. Open Conversation Builder (/whatsapp-business/conversation-builder).
  2. Add a node that accepts components.
  3. Pick saved component instead of rewriting copy.
  4. Publish flow; test on a device with a sandbox contact.

Governance​

  • Name components with version suffix (welcome_v2) when copy changes.
  • Document which broadcast/campaign uses each component in internal runbooks.
  • Archive unused components to keep picker lists short.

Extended guidance​

Component libraries decay without owners—assign a weekly reviewer to delete deprecated buttons. When Meta rejects a template, fix the underlying component first, then republish dependent Conversation Builder paths. Version naming (checkout_v3) prevents editors from selecting retired copy during high-pressure launches.

Practice scenarios​

Build a welcome component, reference it in Conversation Builder, and send a test path to two internal numbers before production.

Sandbox validation​

Repeat the procedure in a test workspace or with two internal colleagues before customer-facing launches. Document who approved each step (marketing, legal, ops). Screenshot Verify your work outcomes for audit trails. When something fails, capture the URL, role, timestamp, and exact UI label clicked—Support resolves tickets faster with that context. Re-read See also links after your first successful run; adjacent topics often cover edge cases you have not hit yet.

Team rollout checklist​

Assign a single owner for this workflow per workspace. Schedule a 30-minute handoff training with screen share. Add the See also links to your internal Notion or wiki. Re-verify after each major product release (labels move occasionally). Pair junior staff with a senior reviewer for the first live execution. Log lessons learned in your team retro—especially permission surprises and integration timeouts.

Keep learning​

Bookmark this page and the Product module map. After major releases, re-walk Step-by-step procedure—UI labels move occasionally. Share feedback with your workspace Admin so Help stays aligned with how your team actually works.

Verify your work​

  • Component visible in builder picker
  • Test conversation renders buttons/lists correctly
  • Edit propagates to draft flows before publish

Tips​

tip

Pair components with WhatsApp Flows when you need form-style data capture beyond quick replies.

Troubleshooting​

| Component not in builder | Save draft; refresh builder session | | Publish fails | Missing required Meta fields on component | | Duplicate labels | Rename—builders filter by name |

See also​