Logs and analytics
Execution history, delivery stats, error handling
Logs and analytics
Automation logs record every send. Use for error handling, dispute resolution, optimization.
Where to find it
/manager/automations/logs. Or on specific automation page → Logs tab.
Per-execution row
Every automation send:
- Timestamp (when sent)
- Automation name (e.g., "Birthday")
- Customer name
- Channel (Email / SMS / WhatsApp)
- Template version (A or B in A/B test)
- Status (Sent / Delivered / Opened / Clicked / Failed)
- Message preview
Status flow
- Sent → Delivered → Opened → Clicked
- If error: Failed or Bounced
SMS
- Sent → Delivered
- If error: Failed
Click tracking on SMS link works too.
Stats endpoint
/automations/stats?id=X&dateFrom=&dateTo=
Per automation:
- Total sent
- Delivered count
- Opened count (email only)
- Clicked count
- Failed count
- Conversion rate (click or goal-based rebooking)
Filtering
On logs filter:
- Date range
- Automation (which)
- Channel (Email / SMS / WhatsApp)
- Status (Failed = troubleshooting)
- Customer name
Error handling
Failed reasons
- Bad customer address (email/phone)
- Opt-out (customer previously unsubscribed)
- Provider transient error (Twilio / SeeMe)
- Missing template variable (e.g., {{appointment_date}} in Birthday automation)
- Frequency cap reached (system skipped)
Solution
- Bad address: fix on customer profile
- Opt-out: respected, not sent
- Provider: wait or ask SuperAdmin
- Bad variable: fix in template editor
- Cap reached: not an error, intentional
Dispute resolution
Customer complains: "I didn't get the booking confirmation email."
- Logs → filter by customer name
- The "Appointment created" automation row
- Status: Sent + Delivered → customer in spam
- Or Failed → email address bad, fix needed
Bulk actions
- Export CSV: logs export to external analytics
- Bulk retry: failed sends retry (admin function)
When to use it
Scenario 1, weekly health check Logs → "last 7 days, Failed." Review list. Many = customer list maintenance.
Scenario 2, A/B test result Stats → filter A vs B version. Open rate, click rate. Activate winner.
Scenario 3, customer dispute Customer claim: didn't get message. Logs → search name. Reply with data.
Scenario 4, ROI analysis "Lapsed customer recovery" automation 60 days, 200 sends. Logs show: 12 customers clicked, 4 rebooked. 2% conversion, not bad.
Scenario 5, template iteration "Appointment reminder" 24h template open rate low. Logs show which subject is effective, template edit.
Tips
- Logs deserve weekly review, don't let them run silently.
- Failed filter is fastest troubleshooting tool.
- Stats endpoint is API-accessible, integrate into external analytics if wanted.
- Bulk retry cautiously, customer may get duplicate.
- Logs stored 6-12 months, older auto-archived.
- Customer dispute 95% answerable from logs if regularly checked.