Follow-ups: create, the login-code check, complete
This chapter covers follow-up tasks — reminders to contact someone: how to create one, what happens when your multi-factor (MFA) code is missing, how "today" and "due" are decided, and how to complete a task.
Before you start — who this is for
Any business member using the CRM tools. Creating a follow-up needs your current MFA code from your authenticator app — have it ready.
Step 1 — create a follow-up
Use the follow-up form to add a task (what to do, and when it is due). Once saved, the task appears in the overview's follow-up card. That card shows only open tasks — never completed ones — with their actual due times.
Step 2 — if your MFA code is missing, the task is not lost
Submitting without your current code is visibly refused, and the refusal is safe:
- The task stays open — nothing is half-created.
- You see a clear, human-readable failure message.
- Enter the current code and submit again; the task then saves.
(The same MFA-refusal-then-retry behaviour applies to contact imports — see Contacts.)
Step 3 — how "today" and "due" are decided
- Due times are shown in your device's time zone, and the screen tells you which time zone it used — you never have to guess.
- "Today" follows the day boundary of that displayed time zone. There is no separate business-level time-zone setting yet — if your team works across time zones, everyone's card follows their own device (an open item, see Not yet covered).
- Overdue, future, undated and completed cases all behave as expected and were each exercised in verification.
Step 4 — complete a follow-up
Use the completion action on the task. It leaves the open-only list, and the overview card recounts from the real records.
If something goes wrong — quick reference
| What you see | What it means | What to do |
|---|---|---|
| Refusal asking for your code | The current MFA code was missing or wrong | Enter the current code and submit again — the task stays open in the meantime |
| A task due "today" at an odd hour | Times follow your device's time zone (shown next to the times) | Check the displayed time zone name; there is no business time-zone setting yet |
Evidence and receipts
- Evidence base:
tools/sms-crm-approved-overview-20261013/(evidence/run06/result.json, 19/19) — the task actions below were exercised through the real existing forms against the actual API. - Evidence kind: locally qualified PASS, real HTTP + ordinary-role disposable PostgreSQL + real browsers, synthetic identity with in-memory native MFA. No live provider, no SMS sent.
| Fact in this chapter | Receipt |
|---|---|
POST /v1/crm/tasks, POST /v1/crm/tasks/:id/status through real forms; MFA refusal leaves task open with human-readable failure before successful explicit retry |
tools/sms-crm-approved-overview-20261013/HANDOFF.md "Persisted actions" paragraph, evidence/run06/result.json (19/19) |
| Open-only list, actual due timestamps, browser time zone displayed, local-day boundary + overdue/future/undated/completed cases | same HANDOFF surface table (follow-ups row) |
| Run04's wrong internal-MFA expectation corrected as test defect | same HANDOFF failure-history paragraph |