Ruby CRM

Record what happened on a call or meeting against a lead. Notes are visible to colleagues who can see the lead, so write them as a handover would read.

add_lead_note

Schedule the next contact with a lead. Always confirm the date, time and channel with the user before calling this — the follow-up appears in their calendar and may trigger a reminder. Times are interpreted in the user's timezone, which get_my_context reports.

create_follow_up

Mark a follow-up done and record how it went. The result note is written onto the lead's timeline, so summarise the outcome rather than just saying 'done'. Completion cannot be undone. Ruby's AI reads a substantive result note and may update the lead's requirements and book, reschedule or cancel their other follow-ups to match — so confirm the outcome with the user before calling this.

complete_follow_up

Produce a wa.me link to a lead with a drafted message pre-filled. This does NOT send anything — it gives the user a link to open and send themselves. Show them the drafted text alongside the link so they can read it before sending. There is no tool that sends WhatsApp messages on their behalf; do not offer to. When lead contact details are hidden from this connection, the link opens Ruby first, which then opens WhatsApp with the draft — give it to the user as it is.

get_whatsapp_send_link

The full record for one lead, including their stated requirements, AI summary and linked listing. Use after search_leads when you need detail the summary does not carry. Call a lead 'Lead #<lead_number>' when you refer to it; never show its id.

get_lead

Full details for one property, including its description, terms and photos. Owner details, documents and agreements are never returned. Show image_urls as an image carousel. If you cannot display a carousel, show cover_image_url as the cover image instead. These URLs are the only photos of the property. Never search the web or use image search for photos of a listing — any photo found that way is of a different property. If you cannot display these URLs as images, give them as links, or show no photo at all. Refer to a property by its reference_number (or its title if it has none), never by its id.

get_listing

Who you are acting as in Ruby and what this connection can and cannot do. Call this first in a new conversation: the user's role decides which leads and listings every other tool will return, so knowing it avoids promising the user something their permissions do not allow.

get_my_context

Leads with WhatsApp activity, most recent message first, so you can answer the question agents ask most: 'who is waiting on a reply from me?'. Use conversation_state='needs_reply' for conversations where the customer spoke last, and 'awaiting_reply' for ones where we did and they have not come back. Any search_leads filter narrows it further. Identify a conversation by the lead's name and phone number, never by an id.

list_whatsapp_conversations

The people in this workspace, with their ids, names, roles, teams, email and phone number. Use this to turn a name into an id — for example to filter leads by the agent they are assigned to — or to find how to reach a colleague. Email and phone come back masked when team member contact details are not shared with this connection. The id is a filter argument only: refer to a colleague by name, and turn an assignee id in another tool's result back into a name with this tool rather than showing the number.

list_team_members

Scheduled follow-ups visible to the signed-in user. Use is_overdue=true for the chase list, or status='pending' with scheduled_at__gte and scheduled_at__lte spanning today to answer 'what's on for today?'. Pass lead to see one lead's history. Refer to a follow-up by its title and time; its uuid is the identifier to use when one is needed. Never show its id.

list_follow_ups