Coastal Care LLC

List Bots

List bots in your Flowly account. Returns id, name, hl_location_id, and created_at for each. Useful when you need to reference a bot by id or name.

List Clients

List clients (the businesses you run bots for) in your account. Returns id, name, location, and experience_level. Use this to look up a client's id when other tools need it.

List Leads

List recent leads across all bots in your account. Returns name, phone, ai_status, last_message_at, and the bot they came from. Optional ai_status filter (e.g. 'engaged', 'handoff', 'cold').

Get Ad Account Summary

Summary of the Meta (Facebook) ad accounts connected to your Flowly account. Returns whether there's an active connection, when its token expires, and the list of attached ad accounts.

List Recent Activity

Recent message activity across your bots. Returns each event's bot_id, contact_id, direction (incoming/outgoing), message text, and timestamp. Use to audit what bots have been doing.

Get Lead AI Runs

Replay the bot's AI decisions for ONE lead — the exact prompt sent to the model and the model's response, turn by turn. This is the best tool for debugging 'why did the bot say/do that?'. First find the lead with list_leads, then pass its id here (or pass a phone number). Each run is one pipeline step: 'generate' = the SMS reply the bot wrote; 'classify' = the handoff / AI-off decision and the reasons it fired (use this to answer 'why did the bot stop / hand off to a human?'); 'extract_booking'

List Hub Escalations

List escalations in the company messaging hub (the internal team surface on app.flowly.biz — NOT client-facing). Each row: id, title, severity (red/yellow/green), status (open = untouched, ack = a human saw it and is on it, resolved = done), the linked client/lead if any, reply_count, and last_activity_at. Use this to check whether an escalation you filed was acknowledged or answered before re-escalating; read the replies with list_hub_messages passing the escalation_id.

List Hub Messages

Read the company messaging hub (internal team surface). Without escalation_id: the team chat — operator messages, EOD notes (kind 'eod'), most recent first. With escalation_id: the reply thread on that escalation (oldest first), including the human replies — use this to check whether Evan answered before re-escalating. Bodies of escalations themselves come from list_hub_escalations.

Update Lead Stage

Move a lead to a different pipeline stage, exactly like the stage picker in the app (recovery workflows are cleaned up automatically on the transition). Valid stages: new_lead, engaged, staff_attention, consult_booked, no_show, cancelled, sold, bad_lead, opted_out, follow_up_later, showed, undecided, hard_no. Find the lead with list_leads first.

Set Lead AI Status

Turn the AI on or off for one lead, exactly like the toggle in the app. 'AI Off' hands the conversation to a human (fires the handoff bundle); 'AI On' resumes the bot (clears handoff state, re-enrolls follow-up when the stage qualifies). Find the lead with list_leads first.

Update Lead Notes

Replace the operator notes on a lead (the Notes field in the app, max 4000 chars). Returns the previous notes so nothing is silently lost — read them first if you mean to append.

Post Hub Message

Post into the company messaging hub (internal team surface — Evan and the team read it in the web app; nothing here ever reaches a client or lead). Three uses: a plain team-chat message (default), the End-of-Day note (kind 'eod' — renders as an EOD card in the chat; batch GREEN items into it), or a follow-up reply on an existing escalation (pass escalation_id from list_hub_escalations). Not for new escalations — file those with post_hub_escalation so they get severity + status tracking.

Post Hub Escalation

File an escalation in the company messaging hub for a human to act on (the escalation channel the CSM skills reference — internal only, never client-facing). Severity: 'red' = urgent, a human needs to look now (pushes to the operators' phones immediately); 'yellow' = same-day; 'green' = cosmetic / low-stakes. Put the full report in body (the BOT ISSUE block format pastes fine); link the client and lead when the escalation is about one so the team can jump straight to them. Check list_hub_escalat