Steps
- Book lands on an allowlisted Calendly sales/discovery event type; the cron (7am/3pm) picks it up.
- The agent researches the booker (socials, business site) and writes a concise prep report.
- Report posts to the owning agency channel, tagging our host (CALENDLY_HOST_SLACK map).
- Adding a new event type: extend EVENT_TYPE_MAP in ~/.hermes/scripts/sales_call_prep.py.
- Adding a new host: extend CALENDLY_HOST_SLACK by Calendly host email.
Cron “RV: Sales call prep” on the Mini (twice daily 7am/3pm, script ~/.hermes/scripts/sales_call_prep.py, agent-driven). Watches Calendly for bookings against an explicit allowlist of sales/discovery event types (generic “Meeting”/“Chat” types never fire this, to avoid noise on non-sales bookings):
- “Jolt Discovery Call” -> jolt, tag Tatem
- “Megaphone Discovery Call” / “Megaphone Demo” -> Megaphone, tag Blake Emal
For each new booking: researches the booker’s socials/business site, writes a very concise Slack-native prep report (who they are, what the business does, notable findings, links), posts to the agency channel tagging whoever it was scheduled with on our side (mapped via CALENDLY_HOST_SLACK in the script by Calendly host email).
Add new sales/discovery event types to EVENT_TYPE_MAP in the script as agencies create them (e.g. a future Lore discovery call type). Add new hosts to CALENDLY_HOST_SLACK by email as team members get their own Calendly booking links.