What Concierge can do
Just ask in plain English, in ChatGPT, Claude, Gemini or the Concierge app, by typing or out loud. Here is every skill your assistant has today, with examples to steal.
New: works in ChatGPT and Claude
Connect Concierge to ChatGPT or Claude and hand it a photo, a spreadsheet or a contract. These skills turn what you give it into contacts, deadlines and prospects.
“Attach a photo of an open house sign-in sheet: "Add everyone on this sheet as leads from the 123 Oak St open house"”
“Attach a purchase contract PDF: "Set up all the deadlines from this contract for the Miller purchase"”
“Find duplicate contacts and anything missing from my records”
“Which past clients have gained the most value in their homes?”
“Find expired listings in 43221 from the last 30 days”
“Sync my latest data from kvCORE”
14 skills in this group
- Sync kvcore
- Pull your latest contacts, transactions and listings from kvCORE right now, instead of waiting for the automatic sync every few hours. Same as the Sync button at the top of every page.
- Import contacts
- Add a whole list of people at once. Paste names and numbers, attach a spreadsheet, or snap a photo of business cards or an open house sign-in sheet. You see a preview first, and anyone already in your contacts is skipped instead of duplicated.
- Onboarding status
- Ask what is set up and what to do next. It offers one step at a time (your clients, your deals, your calendar, your reminder number, a first message, your team), each with several ways to do it, and every one is optional. It never shows keys or passwords.
- Create setup link
- Get a private, one-time link for anything that should not go through a chat: connect kvCORE with your key, upload a contract PDF, make a new API key, get your calendar address, or change your profile photo.
- Snooze setup
- Say "not now" to a setup step and only that step is put off for a week. The others are not affected.
- Set setup step
- Tell it "no thanks" to a setup step and it is never offered again, or "later" and it comes back after a week. Each step is remembered on its own.
- Import records
- Bring in your clients, vendors or past deals from a spreadsheet, a photo or a list. Concierge works out the columns, spots people already in your account, groups couples into households and shows you what it will do before saving anything. Free, and it does not use up your plan.
- Confirm import
- Say yes to a small, clean import and it is saved. Bigger or messier ones come with a link to look them over first.
- Undo import
- Take an import back within 30 days. What it added is removed and what it filled in is put back. Anything you have worked on since is kept.
- List imports
- See what you have imported, whether it finished, and which imports can still be undone.
- Create contract deadlines
- Turn an accepted contract into a full deadline schedule in one step: earnest money, inspection, appraisal, loan commitment, title, final walkthrough and closing. Attach the contract or tell it the dates, and you get reminders for each one.
- Find data issues
- A checkup for your records. Finds people entered twice (even when the phone number is written differently), contacts with no email or phone, and deals missing a client, closing date or price. Nothing changes until you say which ones to fix.
- Get past client equity
- See roughly what your past buyers' homes are worth now and how much they have gained since closing, based on local home sales and, in Franklin County, the auditor's value. A great reason to call. These are estimates, not appraisals, and do not include their mortgage.
- Find expired listings
- Find homes in an area that came off the market without selling (expired, withdrawn or cancelled). Those owners wanted to move and may want a new agent. Check the Do Not Call list before phoning.
Dotloop, calendars & other connections
Connect Dotloop and Concierge can look up your transactions, tasks and documents, and prepare new loops and changes. Connect Google or Apple Calendar and it can put inspections, showings and closings on your calendar. Anything that changes an outside account waits for your approval on a Concierge page.
“What is under contract in Dotloop?”
“Where are we on the Maple Street deal?”
“Create a Dotloop loop for the new Oak Street listing”
“Is my Dotloop connected?”
“Put the inspection on my calendar for Tuesday at 10am”
“Which calendars can you add events to?”
“Put all the Oak Street deadlines on my calendar”
“Move the inspection to Wednesday at 2”
21 skills in this group
- Dotloop list profiles
- See which Dotloop profiles your connected account has.
- Dotloop get profile
- Look at one Dotloop profile, including whether it needs a template.
- Dotloop list loops
- List your Dotloop transactions, filtered by type, status or when they changed.
- Dotloop get loop
- Look at one Dotloop transaction, with its details if you want them.
- Dotloop create loop
- Prepare a new Dotloop transaction. It is created only after you approve it on a Concierge page.
- Dotloop update loop
- Prepare a change to a Dotloop transaction. It is applied only after you approve it.
- Dotloop list contacts
- See the contacts saved in your Dotloop account.
- Dotloop get documents
- See which documents are in a Dotloop transaction.
- Dotloop list tasks
- See the checklist of a Dotloop transaction.
- Dotloop get transaction status
- Where a Dotloop deal stands: status, tasks done, key dates and price.
- Dotloop link loop
- Tie a Dotloop transaction to one of your Concierge transactions.
- Integration get status
- Check whether Dotloop and your other connections are working.
- Integration get action status
- Find out whether a prepared change has been approved and made.
- Showingtime get status
- Check ShowingTime, and see plainly what Concierge cannot do with it yet.
- Calendar list calendars
- See which calendars Concierge can add events to (Google and Apple).
- Calendar create event
- Prepare an event for your Google or Apple calendar. It is added only after you approve it on a Concierge page.
- Calendar add deadlines
- Put every upcoming contract deadline for a deal on your calendar at once, after one approval. Dates already there are skipped.
- Calendar list events
- See the events Concierge has put on your calendar.
- Calendar update event
- Move or change an event Concierge added. It is changed only after you approve, and never if you edited it yourself.
- Calendar delete event
- Remove an event Concierge added, after you approve.
- Disconnect integration
- Disconnect Dotloop or a calendar from Concierge. It asks you to confirm first.
Contacts & Households
Keep every client, couple, and family organized — Concierge files people into households and remembers what matters to them.
“Add Jane and Mark Miller as a new buyer household”
“What do we know about the Smiths' home preferences?”
12 skills in this group
- Find person
- Use when the user mentions one of their own clients, leads or contacts by name or email and you need that individual's record or person ID, e.g. "what's Sarah Miller's phone number?" or "find john@example.com". Searches only the agent's own contacts, not the web. Returns each matching person with ID, email, phone, communication preference, decision-maker flag, their notes and their household's notes. For a whole family or couple ("the Millers"), use find_household instead.
- Find household
- Use when the user refers to one of their own clients as a family, couple or household, e.g. "the Millers", "the Smiths' search" or "pull up the Johnson household". Most tools take a household_id, so call this first to get it. Searches only the agent's own clients. Also use it for "is there anything I should be careful about with [client]?" or "what is [client]'s financial situation?", since the household notes (warnings, financial, preferences) come back with it. Returns household ID, label, type, primary contact ID, referral source, household notes, and each member with ID, email, phone and notes. To find one individual by name or email, use find_person instead.
- Update person
- Use when the user gives new contact details or preferences for one of their own clients, e.g. "Sarah's new number is 614-555-0100", "Mark prefers texts" or "Jen's birthday is April 23". Updates email, phone, preferred channel, best contact time, birthday or decision-maker flag (not the name) and returns which fields changed. Only provide the fields you want to change. Get person_id from find_person. For household-level details use update_household.
- Create person
- Use when the user wants to add a new lead, client or contact to their own database, e.g. "add a new lead, Jane Doe, met her at the open house" or "save my new buyer John Smith". Creates the person and, by default, a household for them (named after the person, or "The [last name]s" for a couple or family). Returns person_id and household_id. Check find_person first so you do not create a duplicate. If they belong in an existing household, set create_household to false and then call add_household_member. It checks the agent's contacts first: the same person is reused, and a similar one comes back as status needs_input with candidates to ask about, so nothing is created until the agent chooses (then pass confirm_new=true for a new person).
- Create household
- Use when the user wants to set up a new client household (the buyer or seller unit a deal belongs to), e.g. "make a household for the Smiths" or "put John and Mary together as the Johnson family". Creates the household and links any existing contacts as members; it can also be created with no members yet. Check find_household first so you do not create a duplicate, and get member IDs from find_person or create_person. Returns the new household_id. To add someone to an existing household use add_household_member. A household with the same name already there comes back as status needs_input; ask the agent, then pass confirm_new=true for a new one.
- List clients
- Use when the user wants to browse or count their own clients rather than find one: "how many clients do I have?", "who is my newest client?", or "list my households". Returns the agent's client households with ID, label, household type, member names and date added, sorted newest first by default, plus a total. It can also sort by contact: sort=recently_contacted answers \"who did I talk to most recently?\" and sort=longest_since_contact answers \"which client have I not been in touch with the longest?\" (households never contacted come first), each row showing the date of the last message or call. To look up a specific client by name use find_household or find_person; to see which leads are hottest use score_leads.
- Add household member
- Use when the user wants to link an existing contact to one of their own client households, e.g. "add Sarah to the Miller household" or "her husband is on this deal too". Both records must already exist: get household_id from find_household and person_id from find_person (or create_person first for someone new). Returns whether the person was added, or says they were already a member.
- Update household
- Use when the user wants to correct or change one of their own client households, e.g. "rename the Millers to the Miller-Grant family", "they're an LLC now" or "their home anniversary is June 3". Changes the household label, type or home purchase anniversary and returns which fields changed. Only include the fields you want to change. Get household_id from find_household. To change an individual's phone, email or birthday use update_person; to add a member use add_household_member.
- Get client preferences
- Use when the user asks what one of their own clients wants or doesn't want, e.g. "what are the Millers looking for?", "what does Rick want in a home?", "what's Sarah's budget?" or "any deal-breakers for the Johnsons?", or before drafting a search or showing recommendation. Returns the saved preference notes (home style, budget ceiling, must-haves, deal-breakers, dislikes), pinned ones first, for a person or for a household and all its members. Give person_id or household_id. For a fuller buyer summary including financial notes, use buyer_needs_summary.
- Delete person
- Use when the user has a duplicate contact to clean up, e.g. "John Smith is in here twice, merge them" or "delete the duplicate Jane Doe". Deletes the person from this system only and does NOT touch kvCORE. Pass merge_into_person_id to first move household membership, notes and messages to the keeper and fill its blank contact, address, status, lead and kvCORE id fields; the result lists how many notes, messages and households moved; without it the person is removed from their households and their notes lose the link. It is meant for duplicates only, not for removing a real contact, and the user should confirm first; get both IDs from find_person.
- Delete household
- Use when the user wants to remove or merge a duplicate client household, e.g. "there are two Smith households, merge them" or "delete that empty household". Deletes from this system only and does NOT touch kvCORE. Pass merge_into_household_id to first move members, transactions, notes and other linked records into the keeper and fill its missing fields. Without a merge target it refuses if the household still has members, transactions or notes. Confirm with the user first; get both IDs from find_household.
- Remove household member
- Move someone out of a household into one of their own, for example after a split. Nobody is deleted and nothing is lost.
Leads & Follow-up
Never let a warm lead go cold. Concierge ranks your sphere, plans daily follow-ups, and flags birthdays and anniversaries.
“Who should I follow up with today?”
“Which clients have birthdays this month?”
8 skills in this group
- Rank leads
- Use when the user asks "who should I follow up with?", "who haven't I talked to in a while?", or "who have I neglected?". Returns the agent's own contacts ranked by days since last logged contact, longest first, with person ID, name, hot, warm or cold rating, lead score, last contact date and days since (contacts never contacted come first). Optionally only those quiet for at least N days. It is not the tool for \"rank my leads\", \"best leads\" or \"hottest leads\": those mean lead quality, so use score_leads. It ranks individual people by recency only (for households sorted by who was last messaged or called, use list_clients); for hot, warm or cold lead scores use score_leads, and for past-client sphere touches use sphere_check.
- Score leads
- Use when the user asks "who are my hottest leads?", "score my contacts", or "update lead temperatures". Recalculates the lead score and hot, warm or cold temperature for all of the agent's own contacts (or one person) from recency of contact, active transactions and deal stage, saves them, and returns hot/warm/cold counts plus the top 10 leads. For who has gone longest without contact use rank_leads or sphere_check; to set a temperature by hand use set_lead_temperature.
- Set lead temperature
- Use when the user wants to mark one of their own contacts hot, warm or cold by hand, e.g. "mark the Johnsons as hot" or "Dave's a cold lead now". Sets that person's lead temperature and returns it. It does not change the numeric lead score, and the next score_leads run (manual or scheduled) recalculates and may replace it. Get the person ID from find_person (for a household, use its primary contact).
- Log open house visitor
- Use when the user tells you about one open house visitor and how interested they were: "log Jenny from the open house, she's hot and pre-approved", "add the couple who asked about offers on Elm St". Creates them as a new lead (or finds an existing contact by exact phone or email), saves a note, sets lead temperature, and for hot or warm visitors adds a follow-up deadline 2 days after the open house. For a whole sign-in sheet with no per-visitor detail, import_contacts is faster. interest_level: hot (asking about offers), warm (thinking about it), looking (casual browsing). Call once per visitor. After all visitors are logged, summarise: "Logged N visitors: X hot, Y warm, Z browsing."
- Follow up planner
- Use when the user asks "who should I call today?", "give me my follow-up list" or "which leads need attention?". Builds a call list from the agent's own client households that have not been contacted recently, ranked by lead temperature (hot, warm, cold), lead score and days since last contact, and flags birthdays in the next 14 days. Returns household ID, name, temperature, lead score, days since contact and a reason. For a pure "who haven't I talked to" list, rank_leads or sphere_check fit better.
- Birthday check
- Use when the user asks about birthdays among their own clients and contacts, e.g. "who has a birthday coming up?", "any birthdays this week?" or "whose birthday is in the next two weeks?". Returns each contact with a birthday on file in the window: name, birthday, days until, household, email and phone, so the agent can send a personal message. For closing anniversaries use anniversary_check; for contacts gone quiet use sphere_check.
- Anniversary check
- Use when the user asks about home anniversaries of their own past clients, e.g. "any closing anniversaries coming up?", "who closed around this time last year?" or "whose home-iversary is this month?". Checks the agent's closed transactions and returns each upcoming anniversary with address, close date, years since closing, days until, and the household name and member first names, a good reason for a personal touchpoint. For birthdays use birthday_check; for contacts gone quiet use sphere_check.
- Sphere check
- Use when the user asks about neglected relationships in their sphere, e.g. "who haven't I talked to in a while?", "who am I neglecting?", or "which past clients should I check in with?". Scans the agent's own households for ones with no logged message in the last N days (30 by default) and returns each with its last contact date, days silent, lead temperature, lead score and referral source, hottest leads first, then longest silence. For a ranked daily call list use follow_up_planner.
Transactions & Pipeline
Track every deal from contract to close — statuses, commissions, deal health scores, and pipeline risk in one place.
“Start a listing transaction at 123 Oak St for the Millers”
“Which of my deals are at risk right now?”
9 skills in this group
- Find transaction
- Use when the user asks about one of their own deals by property address or by client name, or needs a transaction ID, e.g. "what's happening with the Oak Street deal?", "find the Millers' purchase" or "Rick Thomas's listing". Searches only the agent's own transactions (buy or sell side), optionally filtered by status or household. The query can be part of an address ("79 E Gates" finds "79 East Gates Street") or a client's name; it is tried as an address first, then as a client. Returns each match with transaction ID, address, status, type, price, closing date and household ID, plus the notes saved on the deal (disclosures, property details, warnings), so use it for "what should I disclose?" or "what do I know about this house?". To count or list the offers on a deal pass its ID to get_offers; for an overview of every deal, use list_transactions instead.
- Update transaction
- Use when the user reports a change on one of their own deals, e.g. "the Oak St deal is under contract", "closing moved to the 15th", "we got it for 412k" or "that deal fell through". Updates status, closing date, purchase price, address or side (buy, sell, rent, lease) and returns which fields changed. Only provide the fields you want to change. Get the transaction ID from find_transaction or list_transactions. For commission use set_commission; for contract deadlines use reschedule_deadline.
- Delete transaction
- Use only when the user says a deal was entered by mistake or is a duplicate, e.g. "delete the duplicate Oak Street deal". Permanently deletes the transaction and all its deadlines from this system; this cannot be undone. If the deal has offers it refuses and says how many, unless delete_offers is true; tasks and notes that mention the deal are kept and only lose the link; calendar events already created stay in the calendar. It needs confirm=true, which belongs after the user has confirmed. For deals that fell through or were terminated, set the status to "cancelled" with update_transaction instead. Get transaction_id from find_transaction.
- Create transaction
- Use when one of the user's clients starts a new deal, e.g. "we just took the listing at 12 Oak St", "the Millers are under contract on Elm Street" or "start a new buy deal for the Smiths". Creates a transaction (a buy, sell or lease deal on one property) for a client household, optionally with initial deadlines, and returns its transaction_id. Get household_id from find_household (or create_person first for a new client), always validate the address with validate_address first (if it is not found or cannot be checked, say so and ask the agent whether to save it as given), and check find_transaction so you do not create a duplicate. For a full contract timeline use create_contract_deadlines afterwards. If the same address already has a deal for this household, that deal is returned instead of a second one; another household's deal at the address comes back as needs_input (pass confirm_new=true to create anyway).
- List transactions
- Use when the user wants an overview of their own deals: "show me my pipeline", "what do I have under contract?", or "which of my deals close soonest?". Returns the agent's transactions with ID, address, status, buy or sell type, price, closing date and household_id, filtered by status and sorted newest or by closing date, plus a total. To find one deal by address or client use find_transaction; for a broker's whole-office view use get_team_pipeline.
- Get deal health
- Use when the user asks "how are my deals?", "which deals need attention?" or "is the Oak Street closing on track?". Scores the health of one or all of the agent's own open transactions (everything not closed or cancelled). Returns a 0-100 score, green/yellow/red label, named bottlenecks (e.g. "Financing contingency open, closing in 8 days"), days to closing, deadline completion, offer counts and days since last activity. Omit transaction_id to scan all open deals. For a shorter at-risk list, pipeline_risk_report also fits. For each problem, name the specific bottleneck and offer one next action. During morning briefings with 3+ active transactions, call proactively and lead with any red/yellow deals before listing deadlines.
- Set commission
- Use when the user tells you the commission or brokerage split on one of their own deals, e.g. "my commission on Oak Street is 3%" or "I'm on a 70/30 split for that deal". Saves the rate and split on the transaction and returns GCI and agent net, calculated from the purchase price (both are empty if no price is set yet). Get the transaction ID from find_transaction or list_transactions. For totals across deals use get_commission_summary.
- Get commission summary
- Use when the user asks about their own commission or income, e.g. "what's my pipeline worth?", "how much have I made this year?" or "what's my GCI forecast?". Returns, from the agent's own transactions: pipeline volume, GCI and agent net for open deals (active and under contract), closed volume, GCI and agent net for the year, and a per-deal breakdown (25 at a time, open deals first) with price, commission percent and split. If deals_has_more is true, call again with offset set to deals_next_offset for the next page. If missing_commission > 0 in the result, mention it so the agent can fill gaps with set_commission. For conversion rates and lead sources, use get_analytics.
- Pipeline risk report
- Use when the user asks "which of my deals are in trouble?", "what's at risk right now?", or "could anything fall apart before closing?". Scans all of the agent's own active, under contract and pending transactions and returns the flagged ones (most flags first) with address, status, closing date, last contact and risk flags: overdue deadlines, closing within 14 days with deadlines still pending, and no logged client contact in 7+ days. For a 0 to 100 health score on one deal use get_deal_health.
Deadlines & Calendar
Contingencies, closings, and showings with automatic SMS reminders — ask any time what today should look like.
“Remind me about the inspection contingency next Friday”
“What's on my calendar this week?”
9 skills in this group
- Get deadlines
- Use when the user asks about contract dates on their own deals, e.g. "when is the inspection contingency up on Oak Street?", "what deadlines do the Millers have coming up?" or "what's due on my deals this month?". Returns upcoming (not past) contract deadlines such as inspection, financing, appraisal and closing, with deadline ID, title, due date, status and transaction ID, soonest first. For \"is anything overdue?\" or \"what did I miss?\" set include_overdue, which adds deadlines already past due that are still pending, each marked overdue. Filter by transaction (transaction_id, or property with the address words such as \"East Gates\") or household, or omit both for all deals. For a day-by-day calendar that also includes showings, use get_schedule. Also call this when the agent asks for a "what-to-expect" or timeline email for a client: fetch the deadlines, then write a plain-English timeline (no jargon; group by week if many items; buyer perspective = what they do, seller perspective = what the agent handles).
- Get todays priorities
- Use when the user asks "what should I work on today?", "what's urgent?", or "how should I start my day?". Returns a prioritized list from their own data: overdue contract deadlines, deadlines due in the next 3 days, client birthdays and home anniversaries in the next 7 days, and households with an active deal and no logged contact in 30 days. It does not include tasks or showings; use get_tasks and get_schedule for those.
- Complete deadline
- Use when the user says a contract deadline on one of their deals is done or no longer applies, e.g. "the inspection contingency is cleared", "appraisal came in, check that off" or "buyer waived financing". Marks the deadline completed or waived and returns its title and new status. Get deadline_id from get_deadlines first. For to-do items use complete_task instead; to move a date use reschedule_deadline.
- Create deadline
- Use when the user wants one dated item on their calendar with a reminder, e.g. "remind me to call the lender Friday", "add the appraisal deadline for the 15th" or "walkthrough on Oak Street is June 2". Adds a single deadline, milestone or reminder and sends the agent an SMS reminder on the due date. Works for contingencies, walkthroughs, installations, showings or anything dated. ROUTING RULE: if the request says "remind me" or names a specific day or date, use create_deadline. "I need to follow up with the lender" (no date) is create_task instead. For a full contract-to-close schedule use create_contract_deadlines. transaction_id is optional; omit it for personal reminders not tied to a deal.
- Reschedule deadline
- Use when one of the user's own deadlines or appointments moves to a new date: "the inspection contingency got extended to the 15th", "push closing to November 20", or "the showing moved to Friday". Changes only the due date (date only, no time) and returns the deadline title and new date. Get the deadline_id from get_deadlines or get_schedule first. To change the title or other details use update_deadline; to move a to-do task use reschedule_task.
- Delete deadline
- Use when the user wants a deadline, reminder or calendar item removed outright, e.g. "delete that inspection deadline, I added it by mistake" or "remove the walkthrough reminder". Permanently deletes it; this cannot be undone, so confirm with the user first. Get deadline_id from get_deadlines or get_schedule. If the milestone was met or waived, use complete_deadline instead; if the date moved, use reschedule_deadline.
- Update deadline
- Use when the user wants to rename one of their own contract deadlines or appointments, or reopen one closed by mistake, e.g. "rename that to appraisal contingency" or "the inspection deadline isn't actually done, reopen it". Changes the title and/or status (pending, completed, waived) and returns the result. Get the deadline ID from get_deadlines or get_schedule. To change the date use reschedule_deadline; to mark one done use complete_deadline.
- Get schedule
- Use when the user asks about their own calendar, e.g. "what do I have this week?", "am I free Thursday?" or "what's on my calendar?". Returns a day-by-day list for a date range (default: today plus 14 days) of open contract deadlines (not completed or waived) and logged showings, each with ID, title and the related property or household. This is the agent's Concierge data, not an external calendar. For deadlines on one deal or household, use get_deadlines. Narrow the date range for specific-day queries. After suggesting a showing time, offer to log it with create_deadline.
- Suggest showing times
- Use when the user asks when to book a showing for one of their buyer clients, e.g. "when should I show the Millers 123 Main St?" or "find a good time this week for the Johnsons". Returns up to 3 day and time windows for the week, based on the buyer's saved best contact time and how many open contract deadlines the agent has each day (it does not read an external calendar or existing showings). Get household_id from find_household. To record a showing that happened use log_showing.
Tasks
Lightweight to-dos without ceremony — capture them mid-conversation and check them off the same way.
“Add a task to order the for-sale sign”
“What's on my to-do list?”
6 skills in this group
- Create task
- Use when the user wants something on their to-do list, e.g. "I need to follow up with the lender", "add a task to drop off the sign at Oak Street" or "put calling the inspector on my list". Creates an open task (no SMS reminder), optionally linked to a household, transaction or vendor, and returns its task_id. A loose timeframe ("next week") can go in due_date. If a vendor is named, call find_vendor first. For "remind me" or a hard date the agent must not miss, use create_deadline instead (it sends an SMS reminder).
- Get tasks
- Use when the user asks about their own to-do list: "what tasks do I have?", "what's overdue on my list?", or "what do I still need to do for the Miller closing?". Returns the agent's tasks (open by default) with task_id, title, status, priority, due date, overdue flag and linked vendor, sorted overdue first, then by due date. Filter by household, transaction or vendor. Tasks are to-do items; for contract deadlines use get_deadlines, and for the calendar use get_schedule.
- Complete task
- Use when the user says one of their to-do items is finished or dropped, e.g. "mark that task done", "I finished the call with the lender", "cancel the sign task" or "check off the lockbox task". Marks the task done or cancelled and returns its title and status. Use get_tasks first if you need the task_id. For contract deadlines and contingencies use complete_deadline instead.
- Delete task
- Use when the user wants a to-do item removed outright, e.g. "delete that task, I added it by mistake" or "get rid of the duplicate lender task". Permanently deletes the task; this cannot be undone, so confirm with the user first. Get task_id from get_tasks. For finished or dropped tasks prefer complete_task (done or cancelled) so the history is kept. For contract deadlines use delete_deadline.
- Reschedule task
- Use when the user wants to move one of their own to-do tasks to a new due date, e.g. "push that task to Friday" or "move the Miller follow-up to next week". Changes only the due date and returns the task title and new date. Get the task ID from get_tasks first. To rename or reprioritize use update_task; to mark it done use complete_task; to move a contract deadline or contingency date use reschedule_deadline.
- Update task
- Use when the user wants to rename one of their own to-do tasks or change its priority, e.g. "make the lender call urgent" or "change that task to drop off the lockbox". Updates the title and/or priority and returns which fields changed. Get the task ID from get_tasks. To change the due date use reschedule_task. To mark it done use complete_task.
Offers & Listing Prep
Log offers as they land, compare them side by side with a scored matrix, and spin up full pre-listing checklists.
“Log a $415k offer from the Hendersons on 88 Maple Ave”
“Compare all offers on the Duncan listing”
7 skills in this group
- Create listing checklist
- Use when the user takes a new listing and wants the prep scheduled, e.g. "set up listing prep for 12 Oak St", "we just signed the Millers' listing, go live the 1st" or "build my pre-listing checklist". Creates dated deadlines on the seller's transaction, counted back and forward from the target MLS go-live date: photos, staging, pre-listing inspection, disclosures, sign and lockbox, MLS live, first open house and price review. Get transaction_id from find_transaction (or create_transaction first). Use checklist_type="luxury" for high-end properties (over roughly $700k). Running it twice creates duplicates. For a purchase contract timeline use create_contract_deadlines instead. After creating, confirm: "Done. {N} tasks created for [address], starting with photos on [earliest date]."
- Update offer
- Record what happened to an offer: accepted, countered, rejected or withdrawn. It only updates Concierge and messages no one.
- List offers
- See every offer across all your deals, or only the pending ones, or only one property. Same as the Offers page.
- Calculate net proceeds
- Use when the user asks what a seller will walk away with, e.g. "how much will the Smiths walk away with?", "calculate net proceeds on Oak Street" or "what's the seller's net at 450?". Subtracts mortgage payoff, commission, closing costs, seller credits and repairs from the sale price and returns each deduction, total deductions and net proceeds. Commission defaults to 6% and closing costs to 1% of price if unknown; note any assumption.
- Log offer
- Use when the user reports an offer on one of their own deals: "we got an offer on Oak Street", "log a $450k offer from the Millers", or "they countered at 465". Saves an offer linked to the transaction with amount, status, inspection, financing and appraisal contingencies, expiry date and notes, and returns the offer_id. Call find_transaction first to get the transaction_id. To review or compare offers already logged use get_offers or compare_offers. Confirm amount, contingencies (default all three to true), expiry date, and buyer name before logging. After logging, call get_offers to show all offers on that listing. An offer with the same amount and buyer already on the deal comes back as needs_input; pass confirm_new=true to log it anyway.
- Get offers
- Use when the user asks about offers received on one of their own listings, e.g. "show me all offers on Oak Street", "how many offers do we have?" or "what offers came in on the Miller listing?". Returns the address, list price and every offer logged for that transaction, highest amount first, with offer ID, buyer, amount, status, expiration date, inspection, financing and appraisal contingencies, notes and date logged. Name the deal with property (its address words, such as \"East Gates\") or transaction_id, so no lookup is needed first. When the question names a client instead ("how many offers does Rick Thomas have?"), skip that: call find_household and pass its household_id, which returns every offer on the listings of that household and every offer it made. To score and rank offers for the sellers, use compare_offers.
- Compare offers
- Use when the user wants to weigh the offers on one of their own listings, e.g. "help me compare the offers on Oak Street", "which offer is the strongest?" or "rank the offers for the sellers". Ranks pending offers only, scoring price against list price, number of contingencies (inspection, financing, appraisal) and time to offer expiry, and returns each with amount, over or under ask and scores. To just list all offers use get_offers; to record one use log_offer. Ask for the seller's priority (highest price, fewest contingencies, fastest close or balanced) if not stated.
MLS & Market Data
Live Columbus MLS search, new-listing alerts, market stats, comps, and saved buyer searches matched automatically.
“Pull comps for 456 Birch Lane”
“Any new listings in Dublin under $500k?”
8 skills in this group
- Search listings
- Use when the user asks about their OWN listings (properties they represent the seller on), e.g. "what are my active listings?", "which of my listings are under contract?", or "my listings in 43215". Returns the agent's seller-side listings synced from kvCORE or imported, with address, status, price and MLS number, filterable by zip, city, status and price. For any listing on the market (not just the agent's own) use search_mls_listings.
- Search mls listings
- Use when the user wants to search the whole MLS (any brokerage's listings, not just their own), e.g. "what 3-beds are for sale in Dublin under $400k?", "show me pending condos in 43215", or "find homes for a buyer". Queries the Columbus Board of Realtors MLS live through the Spark API, filtering by zip, city, county, price, beds, baths, square feet, year built, property type and status. For the agent's OWN listings use search_listings; for sold comps use get_market_comps. If the result includes a note that it is demo data, tell the user.
- Get market comps
- Use when the user asks for comps, a CMA, or what a home is worth or should list for, e.g. "pull comps for a 3-bed in 43221", "what have 4-bedrooms sold for in Dublin?" or "help me price the Oak Street listing". Searches MLS closed sales (sold listings from any brokerage, newest first) filtered by zip, city, county, price, beds, baths, square footage and months back. Returns each comp with MLS number, address, beds, baths, square feet, year built, list and sold price, close date and days on market. If the result note says demo data, tell the agent. For area-wide averages, use get_market_stats.
- Get market stats
- Use when the user asks about local market conditions, e.g. "what's the market like in 43221?", "how fast are homes selling in Dublin?" or needs numbers for a listing appointment or pricing conversation. Returns MLS area statistics: active inventory count with median list price, days on market and size; pending count; and recent closed sales with median sold price, days on market and average sale-to-list ratio. Medians use a sample of up to 25 listings each. For individual sold comps, use get_market_comps. Summarise as: "In [area] right now, X active listings at median $Y. Homes sitting ~Z days. Recent closes at W% of list." The reply includes a note when the figures come from demo data rather than live MLS data.
- Get new listings
- Use when the user asks what just came on the market, e.g. "what new listings came on this week?", "show me what hit the market in Dublin today" or "any new inventory in 43221 for the Millers?". Returns active MLS listings from any brokerage first listed within the last N days, newest first, filtered by area, price, beds, baths and property type. Each has MLS number, address, price, beds, baths, square feet, listing agent and office. If the result note says demo data, tell the agent. For the agent's own listings, use search_listings; for any active MLS listing regardless of age, use search_mls_listings.
- Match buyer to listings
- Use when the user wants homes for one of their own buyer clients: "find listings for the Millers", "what's on the market for the Garcias?", or "match my buyer to inventory". Searches active MLS listings with the filters you pass and returns the buyer household's saved preference notes alongside them. The preference notes are not applied as filters automatically, so read them (or call get_client_preferences first) and pass budget, beds, area and so on as filters. Call find_household first for the household_id. Results may come from a demo dataset; say so when the result includes that note. For a search not tied to a client use search_mls_listings. Lead with 2 or 3 top picks each with a one-sentence "why this fits", then mention any clear misses.
- Save buyer search
- Use when the user wants to save or change a buyer client's home search criteria, e.g. "save a search for the Smiths", "the Joneses want 3-bed homes under $400k in 43209", or "update their search". Stores the criteria (beds, baths, price range, zip codes, keywords) on the buyer household and returns the search ID; active searches are checked nightly for new MLS matches. Pass search_id to update an existing search instead of creating a duplicate. Get household_id from find_household. To run searches now use check_saved_searches or match_buyer_to_listings.
- Check saved searches
- Use when the user asks whether anything new hit the MLS for their own buyers' saved searches, e.g. "any new listings for the Smiths?", "check my buyer searches" or "what new homes match the Joneses' criteria?". Runs each active saved search against the MLS for listings new or changed since that search was last checked (last 7 days if never), up to 10 per search, and marks it checked. Returns matches grouped by search and household. Results may be MLS demo data; pass on the note if one is returned. To create a search use save_buyer_search; for an ad hoc match use match_buyer_to_listings.
Property Records & Calculators
Ohio county auditor records, address checking, affordability math, net-proceeds, and investment analysis on demand.
“Who owns 789 Cedar Ct and what did they pay for it?”
“Run investment numbers on a $300k duplex renting for $2,600”
5 skills in this group
- Validate address
- Use when the user says "validate this address" or "is this address right?", and before saving any address to a transaction, household or person. Checks a US street address against US Census street records and returns the tidied form with its ZIP code, which is the form to store. It does not check unit numbers or mail delivery. If the address is not found, tell the agent and ask them to confirm it; new or rural addresses are sometimes missing, so save it as given if they confirm. If the result has checked: false, the check could not run: say so and ask whether to save it as given. For ownership records, assessed value, parcel data, or school district lookups, use lookup_property instead.
- Buyer affordability calculator
- Use when the user asks what a buyer can afford, e.g. "how much can the Millers afford?", "what price range should we show?" or "calculate their max purchase price". Estimates purchase power from income, monthly debts, down payment and rate using conventional 28/43 DTI limits; this is an estimate, not a pre-approval. Returns max purchase price, conservative price (80% of max), loan amount, down payment percent, monthly breakdown (P&I, tax, HOA, total) and DTI at max. Both the maximum and the conservative figure are returned. If DTI at max is over 40%, flag: "This is near the conventional lending limit. Lender pre-approval will be the real test."
- Investment property analysis
- Use when the user asks "what's the cap rate on this?", "is this a good rental?", or "run the numbers on this income property" for an investor client. Calculates with exact arithmetic from the numbers given (no lookup of the property): NOI, cap rate, cash-on-cash return (cash invested includes an estimated 2% closing cost), monthly principal and interest, monthly and annual cash flow, gross rent multiplier, break-even occupancy and an expense breakdown. Taxes and insurance are estimated if not given. Present: cap rate, cash-on-cash, monthly cash flow, GRM, break-even occupancy, then a plain-language verdict. Benchmarks: cap rate >6%=solid, 4 to 6%=market-rate, <4%=appreciation play; cash-on-cash >8%=strong, 5 to 8%=acceptable; GRM <12=favorable. If cash flow is negative, state it clearly.
- Lookup property
- Use when the user asks "who owns 123 High St?", "look up this parcel", "what is it assessed at?", or "find properties owned by [name]". Returns public Ohio county auditor records for any property, not the agent's own data: parcel ID, owner name, property type, square footage, acres, year built, beds and baths where recorded, assessed, land and building values, last sale price and date, homestead, and school and tax district. Supports Franklin, Delaware, Union, Fairfield, Licking, Madison, Pickaway, Perry, and Hocking counties. Accepts a street address ("123 High St Columbus"), a parcel ID ("234-000007"), or an owner name ("Rick Thomas" or "Thomas Rick", word order does not matter). For owner name searches, include the county. For an owner name, search the first and last name; a middle name is optional because county records often hold only an initial or none, so "Richard Paul Thomas" still finds "THOMAS RICHARD". Results are ranked best match first and each shows the second (co-)owner when there is one, so use that to tell similar names apart. If the reply says more matches exist than were shown, ask the user for a street, ZIP or spouse name to narrow it, or look the address up directly; do not tell the user the search is unreliable. For listing price, status or photos use search_mls_listings (any MLS listing) or search_listings (the agent's own listings). For checking that a street address exists or tidying it, use validate_address instead.
- Search nearby properties
- Use when the user asks what parcels surround a property in central Ohio, e.g. "who are the neighbors on that street?" or "what's around my seller's house?". Give a street address, or a latitude and longitude. Returns county auditor parcels within a radius: parcel ID, address, owner, property type, square feet, acres and assessed value (the nearest 12). An address is looked up with the US Census geocoder, which also finds the county; with coordinates you must name the county. This is public record data, not MLS sales: for sold comps or a CMA use get_market_comps, and for one property's owner or value use lookup_property. Radius defaults to 400 meters (about a quarter mile).
Showings & Buyer Reports
Log feedback after every showing, then turn it into recaps, home-comparison reports, and meeting-prep briefs.
“The Parkers loved the kitchen at 12 Elm but hated the yard”
“Prep me for my 2pm meeting with the Wilsons”
6 skills in this group
- Log showing
- Use when the user reports how a showing went for one of their own buyer clients: "the Millers loved 45 Elm St", "log the showing, they said maybe, kitchen too small", or "we toured Oak Ave today, not a fit". Saves a showing record with address, MLS number, date, rating (loved, maybe or no) and feedback, and returns its ID. Call find_household first for the household_id. For an open house visitor use log_open_house_visitor; to schedule a future showing use create_deadline.
- Get showings
- Use when the user asks which homes a buyer has seen or what buyers thought of a property, e.g. "what houses have we shown the Millers?", "which ones did the Johnsons love?" or "what feedback did we get on 123 Oak St?". Returns the agent's own logged showings for a buyer household or a property address, newest first, with showing ID, address, MLS number, date, rating (Loved it, Maybe, Not a fit), feedback and household ID. Give household_id or address. For a written recap of today's tour, use get_showing_recap; for upcoming dates, get_schedule.
- Get showing recap
- Use when the user says "recap today's showings for the Millers", "summarize the tour" or "write up how the showings went". Loads one buyer household's recently logged showings (address, MLS number, date, rating, feedback), its members and its preference notes so you can write a post-tour recap. Covers today and yesterday by default; pass days_back (up to 60) when the agent asks to recap all of a client's showings rather than today's. For showing history by address or older than that, use get_showings. After the tool returns, write four sections: 1. Rankings: homes in order from most to least loved, one-line reason each. 2. What stood out: 2 to 3 specific things buyers responded to. 3. Patterns: what today reveals about what they really want. 4. Draft follow-up: warm, concise message with thanks, favourite home, next step. Show the draft; do not send it unless the agent asks. If no showings logged, say: "No showings recorded. Use log_showing to add each property first."
- Meeting prep brief
- Use when the user is about to talk to one of their own clients: "brief me on the Millers before my call", "prep me for my listing appointment with the Johnsons", or "what do I need to know before I meet the Garcias?". Returns the household, its members with contact details, lead temperature, lead score and contact preference, referral source, their active deal (address, status, price, closing), preference notes, recent notes and the last logged contact. Call find_household first for the household_id. For deal risks on a transaction use get_deal_health.
- Home comparison report
- Use when the user wants to compare homes their own buyer client has toured: "compare the homes the Millers have seen", "which house is the best fit for the Garcias?", or "recap the ones they loved" or "compare 418 Oak Hill Drive and 1507 Linden Avenue for the Garcias" (homes they have toured; it is the first tool to call for comparing homes a client has seen). Returns that household's logged showings (address, MLS number, date, rating, feedback), newest first, plus the buyer's saved preference notes. You write the comparison after the tool returns. Call find_household first to get the household_id. For a recap of one showing use get_showing_recap.
- Buyer needs summary
- Use when the user asks what one of their own buyers is looking for, e.g. "what does this buyer want?", "summarize the Millers' needs", or before running an MLS search or match_buyer_to_listings. Loads the household's saved search criteria (beds, baths, price range, ZIPs), preference, warning and financial notes plus showings they rated loved, maybe or no with feedback. You write the needs summary after it returns. Get household_id from find_household. For raw preference notes only, get_client_preferences is lighter.
Messaging & Call Logs
Send SMS and email straight from chat, log calls, and build a library of reusable message templates.
“Text the Duncans that closing moved to the 15th”
“Save that as my inspection reminder template”
7 skills in this group
- Send message to household
- Use when the user asks to text or email one of their clients or a whole household, e.g. "text the Millers that the inspection is Tuesday". Always use this tool to draft a message to a client, never write one in chat yourself: only this tool logs the draft and gives the tap-to-send link. Pass household_id to reach all members (one link per channel; use a generic greeting such as "Hi all", since {name} is not filled in) or person_id for one contact. Each person's preferred channel is used unless you force one; anyone missing a phone or email, or who prefers calls, comes back under failures. Get IDs from find_household or find_person. The reply has show_to_user: the draft and its tap-to-send link. Show it to the agent exactly as written with the link tappable. Nothing is sent until the agent taps the link and presses send in their own messages or mail app, so never say it was sent.
- Get communication history
- Use when the user asks what they have sent or said to one of their own clients, e.g. "what have we sent the Smiths?", "when did I last talk to Sarah?" or "show my texts with the Millers". Returns the logged emails, texts and call summaries for a household or person, newest first, with date, channel, direction, status and the first 200 characters of each. Give household_id or person_id (household_id wins if both are given).
- Log call summary
- Use when the user reports a conversation with one of their own clients or leads that happened outside Concierge: "I just got off a call with Sarah Miller", "the Garcias texted me saying...", or "I got an email from my seller". Saves the summary to that person's communication history and returns the communication_id. It sends nothing. Call find_person first to get the person_id. Use channel = call/sms/email and direction = inbound/outbound.
- Update message template
- Change a saved message template: its name, channel, subject or wording.
- Delete message template
- Delete a saved message template. It asks you to say yes first.
- Save message template
- Use only when the user explicitly asks to keep a message you just drafted for reuse, e.g. "save that as a template" or "keep that as my closing reminder". Saves it to the agent's own template library and returns the template ID and saved body. Recall it later with find_message_template. Templates are reused for other clients, so the body should have specific names, addresses, prices and dates replaced with placeholders before it is saved. Supported placeholders: {{recipient_first_name}}, {{recipient_last_name}}, {{recipient_full_name}}, {{household_name}}, {{property_address}}, {{closing_date}}, {{purchase_price}}, {{agent_first_name}}, {{agent_full_name}}, {{agency_name}}, {{today}}, {{tomorrow}}. After saving, echo back the saved template body and confirm: "Saved as '[name]'. I swapped in placeholders where the specifics go." If the original draft had nothing to replace (no concrete names/addresses), save it as-is.
- Find message template
- Use when the user asks to "use my [X] template", "send the under contract template to the Millers", or "what templates do I have?". Finds the agent's own saved email and text message templates (up to 10, most recently used first). Returns each template with template_id, name, channel, subject, tags, usage count and its raw body containing {{placeholders}} like {{recipient_first_name}}, {{property_address}}, {{closing_date}}. NEXT STEPS after this tool returns a template: (1) substitute every {{placeholder}} in body and subject with values from current context, calling find_household or find_transaction first if the recipient or property is not already loaded; (2) show the filled-in draft to the user and send only when they clearly ask, by calling send_message_to_household with the filled-in text as the "message" parameter (NOT "body"), the filled-in subject as "subject", AND template_id set to this template_id so usage is tracked. Do not show the raw template with placeholders to the agent; always render it first.
Vendors & Referrals
Your inspector, lender, and title network — with referral tracking that shows who sends business back.
“Add Apex Inspections to my vendor list”
“Which lender have I referred the most this year?”
6 skills in this group
- Find vendor
- Use when the user asks for someone in their own vendor network, e.g. "who's my go-to inspector?", "get me Mike's number at First Ohio" or "list my lenders". Searches the agent's saved vendors (inspectors, lenders, attorneys, title companies, contractors, appraisers) by name, company or type, not the web. Returns vendor ID, name, company, type, phone, email and contact person. Call this to get a vendor_id before updating, deleting or logging a referral. For referral rankings, use get_referral_partners.
- Create vendor
- Use when the user wants to save a new service provider to their own vendor list, e.g. "add my lender Mike Jones at ABC Mortgage", "save this inspector's number" or "add a new stager". Creates a vendor (inspector, lender, attorney, title company, contractor, appraiser, photographer, stager, etc.) with any notes saved as a vendor note, and returns its vendor_id. Check find_vendor first so you do not create a duplicate.
- Update vendor
- Use when the user gives new details for someone in their own vendor network, e.g. "Mike at First Ohio has a new email" or "Dana moved to a different title company". Updates the vendor's name, type, company, phone or email and returns which fields changed. Only provide the fields you want to change. Get vendor_id from find_vendor.
- Delete vendor
- Use when the user asks to remove a vendor from their own network because it was added by mistake or is a duplicate, e.g. "delete that duplicate inspector" or "remove Mike's lender entry". Permanently deletes the vendor (inspector, lender, attorney, title company, contractor) and cannot be undone, so confirm with the user first. Get the vendor_id from find_vendor. Returns the deleted vendor's ID and name.
- Log referral
- Use when the user sends a client to, or gets a client from, one of their own vendors (lender, title rep, inspector, etc.): "I sent the Smiths to Mike at First Ohio", "log a referral to Sarah's inspector", or "John at Heartland Title referred me a buyer". Saves the referral as a note on the vendor (direction, details, any fee owed) and returns the note_id. Call find_vendor first to get the vendor_id. To see who refers the most business use get_referral_partners.
- Get referral partners
- Use when the user asks about referral relationships with their own vendors, e.g. "who are my best referral partners?", "which lenders do I send the most business to?" or "who has sent me referrals lately?". Ranks the agent's vendors by the referrals logged with log_referral, sent or received. Returns vendor ID, name, type, referral count, last referral date and any "fee owed" notes; vendors with no referrals fill out the list. To look up a vendor's contact details, use find_vendor.
Notes & Memory
Attach notes to anyone or anything — and Concierge itself remembers your preferences, phrasing, and corrections.
“Note that the Kims prefer evening showings”
“Remember that I always call closings 'settlements'”
6 skills in this group
- Create note
- Use when the user tells you something worth remembering about one of their own clients, deals or vendors, e.g. "the Millers hate carpet", "note that the seller is relocating for work" or "this inspector is always late". Saves a note on a person, household, transaction or vendor. Use category="preference" with pinned=true when a client wants, dislikes or requires something, and save it immediately without asking for confirmation. Use category="warning" for red flags and category="timeline" for follow-up context. Get entity_id from the matching find tool. Confirm briefly: "Got it, I've noted that."
- Update note
- Use when the user wants to correct, rewrite, pin or unpin one of their existing notes on a client, e.g. "change that note to say they're pre-approved for $450k" or "pin the note about the dog". Replaces the note text and/or sets pinned, and returns which fields changed. Note IDs come from the notes returned by find_person or find_household. To add a new note use create_note.
- Delete note
- Use when the user wants a saved note on one of their clients, deals or vendors removed, e.g. "delete that note about the Millers' budget" or "that note was wrong, remove it". Permanently deletes it; this cannot be undone, so confirm with the user first. Get note_id from the notes that find_person or find_household return. To keep the note but change its content, use update_note instead.
- Remember
- Use when you notice something lasting about how the agent likes to work: a preference, a correction, a terminology quirk or a workflow pattern, such as "always call my buyers clients" or "I never do open houses on Sundays". Saves it to the agent's memory and returns saved: true. Call this silently when you notice something worth remembering. Do NOT mention to the agent that you saved a memory. This is about the agent, not their clients; for client details use create_note.
- Forget memory
- Use when the user says "forget that", "that's wrong" or "don't remember that" about something you remembered about them or one of their clients. Permanently deletes one saved memory by ID. Find the correct ID first in the memories already in your context (under headings like "## What I Know About [name]"); never guess an ID. Returns the deleted memory ID, or an error if it is not found for this agent.
- List memories
- Use when the user asks "what do you remember about me?" or "what have you saved about how I work?", and always before forget_memory so you have the correct ID to delete. Returns every saved memory about the agent (their preferences and habits, saved with remember) with ID, category, content, confidence score, use count and date saved. These are notes about the agent, not client notes; for client notes use the person or household tools.
Automation & Notifications
Set rules that fire on their own — when a condition is met, Concierge takes the action or pings you in-app.
“When a closing date is set, remind me 30 days out to schedule the walkthrough”
“Notify me Monday at 8am to review my pipeline”
8 skills in this group
- Create workflow rule
- Use when the user wants a standing automation across their contacts, e.g. "remind me when I haven't contacted someone in 30 days", "alert me if a lead goes cold" or "remind me a week before client birthdays". Creates an active rule, checked on a schedule for each contact. Conditions: contact_stale (not contacted in {days} days), birthday_soon (birthday within {days_ahead} days), no_response (outbound message {days}+ days ago with no reply), lead_temperature_is (lead temperature equals {temperature}). Actions: notify_agent (adds a reminder deadline due today, params: message) and create_deadline (adds a reminder deadline, params: title, days_from_now). {name} in the text becomes the contact's first name. For a one-off reminder use create_deadline; to see rules use list_workflow_rules.
- List workflow rules
- Use when the user asks "what automations do I have set up?", "show me my workflow rules", or before changing or deleting one. Returns all of the agent's automation rules, active and paused, newest first, each with ID, label, trigger condition and its settings, action and its settings, an is_active flag and the date created. Use the ID with delete_workflow_rule; to add one use create_workflow_rule.
- Delete workflow rule
- Use when the user asks to turn off, remove or delete one of their own automations, e.g. "stop the closing reminder automation" or "delete that workflow rule". Permanently deletes the workflow rule, so confirm which rule with the user first. Call list_workflow_rules first to get the rule ID; never guess it. Returns the deleted rule ID, or an error if the rule is not found or belongs to someone else.
- Get notifications
- See your alerts, the ones the bell shows on the dashboard, with unread first.
- Mark notifications read
- Clear your alerts, all of them or just some.
- Update reminder phone
- See, change or remove the mobile number your deadline reminders and daily brief are texted to.
- Notify agent
- Use when the user asks you to send them a notification now: "ping me with that", "send this to my notifications". Sends an in-app notification to the agent themselves (never to a client) and returns sent: true. For a reminder at a later time use schedule_notification; for a dated to-do use create_task.
- Schedule notification
- Use when the user wants a reminder for themselves at a specific future date and time, e.g. "remind me tomorrow at 9 to call the lender", "ping me Friday about the Oak St inspection", or "remind me in 3 days". Schedules an in-app notification for the agent (not a text or email to a client) and returns its ID and fire time. Times are the agent's local time (Eastern unless told otherwise); the time must be in the future. For a notification right now use notify_agent; for a to-do item use create_task; for a contract date use create_deadline.
Business Analytics
Conversion rates, GCI by quarter, time-to-close, and a weekly business review generated from your real numbers.
“Run my weekly business review”
“What's my GCI this quarter?”
4 skills in this group
- Get analytics
- Use when the user asks how their own business is performing over a year, e.g. "how is my business doing this year?", "what's my conversion rate?" or "where do my clients come from?". Returns, from the agent's own deals and clients: the pipeline funnel (active, under contract, closed) with conversion rates, average days to close, volume by deal type, GCI and agent net by quarter, client households by referral source, and a hot/warm/cold lead count. For pipeline and commission dollars by deal, use get_commission_summary.
- Get dashboard summary
- Your dashboard in one answer: pipeline value, deals closed this year, new contacts, lead temperature, deadline health and what is due next.
- Get plan status
- Ask what plan you are on, how many trial days are left and how much of the month you have used. It never takes payment or asks for card details.
- Weekly business review
- Use when the user asks "how did I do this week?", "give me my weekly review", "summarize my business this week" or "WBR". Returns the agent's own weekly numbers: deals by status (active, under contract, pending), closings this week, pipeline value, new households, showings, messages sent, overdue deadlines and deadlines due in the next 7 days. You write the review after the tool returns. For what to do today use get_todays_priorities; for deals at risk use pipeline_risk_report.
Brokerage & Team
Broker tools: team-wide pipeline visibility, agent onboarding invites, roles, and MLS profile sync.
“Show me the whole team pipeline”
“Invite a new agent to the brokerage”
8 skills in this group
- Update agent profile
- Use when the user says "update my profile", "call me Rick from now on", "I prefer short answers", "I mostly work with first-time buyers", or asks to see their profile. Views or changes the agent's own assistant profile notes, the free-text bio that shapes how the assistant addresses and works with them in every conversation. Returns the profile text. action=append for additions, action=set to replace, action=get to show.
- Get team overview
- Use when a broker asks about the whole office: "how is my team doing?", "show me everyone's pipeline", or "which agent has the most overdue deadlines?". Returns one row per agent in the brokerage with role, active deal count, pipeline value in dollars (active, under contract and pending), and overdue and due-this-week deadline counts, sorted by most active deals. Only works for brokers and admins. For the individual deals across the team, use get_team_pipeline.
- Get team pipeline
- Use when a broker asks about deals across the whole office: "show me all open deals on the team", "which team deals close this month?", or "what is everyone under contract on?". Returns every agent's transactions with agent name, transaction ID, address, status, price and closing date, sorted by closing date. Only works for brokers and admins. For per-agent totals use get_team_overview; for the user's own deals use list_transactions.
- Set agent role
- Use when a broker or office admin wants to see or change a team member's role, e.g. "make Jane a transaction coordinator", "promote Mike to broker", or "what role does Tom have?". Reads or sets the role of another agent in the same brokerage and returns the role. Only works when the signed-in user is a broker or admin, and only for agents in their own agency. Roles: broker, agent, tc (transaction coordinator), admin. Get the agent's ID from get_team_overview.
- Sync mls agent id
- Use when the user asks "what is my MLS ID?", "what's my agent ID in the MLS?", or "sync my MLS agent ID". With action get, returns the MLS member ID already saved on the agent's profile. With sync (the default), finds the agent's user in kvCORE by email, saves its MLS ID to the profile and returns it. Sync requires a kvCORE API key in the agent's settings.
- Get team roster
- For the agency owner: who has joined the team, how busy they are, what they have cost in AI, and the invite code.
- Send password reset
- Email yourself the usual set-a-new-password link, sent only to the address already on your account.
- Invite agent
- Use when the agency owner wants to bring a new agent onto their team in Concierge: "invite Sarah to join my brokerage", "send Mike an invite". Drafts an email and/or text to that agent with the agency's invite code and an onboarding link. Nothing is sent by Concierge: the reply has a tap-to-send link for each draft that opens the agent's own email or messages app, plus the code and link. Only the agency owner can use it; the tool enforces this. This is not for clients; to message a client household use send_message_to_household. Before calling, confirm you have the agent's name and at least one of email address or mobile phone, and confirm with the user before sending.
More skills
Additional abilities that keep Concierge improving.
5 skills in this group
- Resolve record
- Use before creating anything, or when a name or address might match more than one record: "is Rick Thomas already in my contacts?", "do I already have a deal at 79 E Gates?". Looks up a person, household or deal by how it is written (nicknames, abbreviations, phone formats and address styles are handled) and returns every possible match with facts that tell them apart. Never picks one for you: if there are several, show them and ask. Writes nothing.
- Approve change
- Use only after the agent has said yes to a preview that another tool returned with status needs_approval (a merge, a delete with linked records, an import undo). Carries out exactly that previewed change. Send the action_id and approval_hash from that reply; they must match what the agent was shown. Works once, only for the same agent, and not after the preview expires. Never call it on your own to get a change through: if the agent has not clearly said yes to this preview, ask. A few changes (such as role changes) can only be approved at the approval_url in the browser.
- Find client
- Use when the user names one of their clients, buyers, sellers or contacts, by person, couple or family: "Rick Thomas", "the Millers", "find john@example.com", "who is the buyer on Oak Street?". Searches the agent's own contacts and households together and returns each household with its members, and each matching person, with person ID, household ID, email, phone, communication preference and how many notes there are. The IDs it returns are the ones every other tool wants. Several matches mean ask which one; never choose. For the full picture of one client (deals, deadlines, tasks, offers, last contact), then use get_client_overview.
- Get client overview
- Use for the whole picture of one client in a single call: "tell me about the Millers", "what is going on with Rick and Ashley?", "catch me up on this client". Returns the household with member ids, their active deals, open deadlines, open tasks, offers and the date of the last message or call. Get household_id from find_client. For one narrow question (just the offers, just the deadlines) the specific tool is lighter.
- Who to contact
- Use when the user asks who to reach out to: "who should I follow up with?", "who haven't I talked to in a while?", "who needs a touch this week?", "any birthdays or home anniversaries coming up?". Returns the agent's own client households ranked by days since the last logged message or call to anyone in them, longest first (never-contacted first). Set client_type to lead to rank individual leads instead, and milestones to true to add birthdays and home anniversaries in the next 14 days. It does not rate lead quality (hot, warm, cold); for that use score_leads.
Skills are added regularly — if Concierge can't do something yet, just ask for it and it will be logged as a request.
