Assign & Follow Up on Campaign Replies
Route campaign responses to Smart Inbox, assign ownership, qualify the lead, and create the next task or pipeline action.
Step-by-step instructions
- Define reply ownership before launch.
- Route responses to Smart Inbox.
- Apply the campaign source, tags, and fields.
- Assign the conversation.
- Qualify the response.
- Create a task, follow-up, appointment, order, or pipeline action.
- Honor opt-outs immediately.
Who should use it
Marketing users, sales teams, workspace managers and authorized campaign operators.
Where to find it in Wemblo
Wemblo -> Marketing -> Social Engagement
Before you begin
- Use the correct workspace and connected channel.
- Confirm audience consent and provider eligibility.
- Prepare fictional test contacts and approved content.
- Assign a person or team to handle replies.
Main concepts and fields
| Concept / Field | Meaning or Use |
|---|---|
| Campaign | Planned communication to an audience. |
| Sender | Connected channel identity. |
| Template / Content | Approved message or post. |
| Schedule | Immediate or future launch. |
| Reply Owner | Team or user responsible for responses. |
Test and verification
- Complete one successful path with fictional data.
- Complete one invalid, failure or permission path.
- Confirm the result appears in the correct workspace and module.
- Confirm the correct person or team can review and continue the work.
Common issues and solutions
| Issue | What to Check |
|---|---|
| Campaign or post cannot start | Sender, destination, audience, consent, schedule and plan limit. |
| Content or variable fails | Template/content status, field mapping and fallback value. |
| Provider reports failure | Authorization, media/content rules and provider response. |
| Replies are missed | Smart Inbox routing, assignment and staffing. |
Security, privacy, consent, cost and provider notes
- Use only data the business is authorized to process.
- External provider charges, policies, approvals, limits and availability remain separate.
- Do not expose passwords, API keys, tokens, webhook secrets, payment credentials or private customer data.
- Use human review for sensitive, regulated, urgent, financial or final decisions.
Last reviewed: