Campaigns
A campaign sends an approved template to many recipients. Calypso distinguishes Campaign (a send to a list) from Re-contact (a follow-up to people you have spoken to before).
Building one
- Name it. Something you will recognise later —
January onboarding, nottest 3. - Pick the template. It must be approved. If it uses variables, you will be asked to supply them.
- Add recipients. Upload a CSV or add them manually.
- Map the columns. Confirm which column holds the phone number, and how the remaining columns map to template variables and to client fields.
- Review and send.
CSV mapping
Calypso proposes a mapping and asks you to confirm it rather than guessing silently. Two different things can come out of your CSV:
- Template variables — values substituted into the message each recipient receives.
- Client fields — extra details (department, tags, reference numbers, notes) copied onto the customer record. These are for your team and are not sent to recipients.
Confirm the phone column carefully; it is the one mistake that is expensive.
While it runs
A campaign can be paused from its detail view. Pausing stops further sends; messages already delivered are not recalled.
After it runs
The campaign detail view carries delivery and performance information for that send. Replies arrive as ordinary conversations and land on boards under the usual membership rules — a campaign reply is a conversation like any other, and the board's agent will handle it if that board is switched on.