/docs/modules/follow-ups
Follow-ups
Keep the next touch honest — who owns it, when it is due, and what happened.
Purpose
Follow-ups are time-bound CRM chase items (call back, send docs, check funding) separate from generic desk to-dos. They surface in notifications when due and sit next to Tasks and Calendar in the daily ops stack.
Open in app: app.flashfender.com/follow-ups.
How this fits with Tasks & Calendar
| Surface | Best for |
|---|---|
| Follow-ups | Lead/customer chase with a due date and outcome |
| Tasks | Desk to-dos across deals, docs, recon — broader types |
| Calendar | Appointments and test drives (time blocks) |
Many desks use all three: book the drive on Calendar, chase no-shows on Follow-ups, park internal paperwork on Tasks.
Setup
- Confirm staff can open Follow-ups (role permissions).
- Train BDC: every working lead should have a next follow-up or task with a due date.
- Optional: watch the header bell — due follow-ups appear in the notifications feed when configured.
Daily workflow
- Open Follow-ups (or start from a lead/customer record).
- Create with due date, owner, and related lead/customer.
- Work the due today queue before new inbound.
- Complete with a short outcome note — feeds the activity timeline.
- Reschedule no-answers instead of leaving overdue noise.
Key fields
| Field | Notes |
|---|---|
| Due date | Drives sort and notifications |
| Owner | Single accountable rep |
| Related record | Lead and/or customer |
| Status | Open / done / cancelled |
| Outcome notes | What the buyer said; next step |
Permissions
- BDC / Sales — create and complete own follow-ups; see team queue if role allows.
- Manager — reassign, clear overdue bulk, audit outcomes.
Canadian notes
- CASL: a follow-up labeled “send promo” still needs consent on the customer record before automated email/SMS.
- Compliance chases (disclosure acknowledgement, funding stipulations) belong in notes — not a silent checkbox.