Have something to say?
Public API / MCP Server for Appointwise
The problem: There's currently no way to interact with Appointwise programmatically. Everything — creating sub-accounts, setting up agents, configuring details — has to be done manually in the UI. For agencies running automated operations, Appointwise ends up being the one platform in the stack that can't plug into their workflows. Feature request: A public API (and ideally an MCP server on top of it) that exposes core platform actions, such as: Create/manage sub-accounts Create agents, or duplicate an existing agent as a template Update agent details and variables (business info, services, calendars, etc.) Webhook triggers for key events Example use case: My client onboarding is almost fully automated — payment comes in, the onboarding form data flows through n8n, and sub-accounts and systems get spun up automatically. Appointwise is the one manual step left. With an API, the flow would be: payment received → pull onboarding form data → create sub-account → duplicate a proven agent template with the client's details injected → their AI setter is live within minutes of payment. That's just one example — an API opens up all kinds of workflows: syncing data to reporting dashboards, bulk updates across clients, integrating with any CRM or automation platform, letting AI tools like Claude manage configuration. Why it matters: Agencies are your highest-leverage customer segment, and agencies run on automation. An API/MCP server turns Appointwise from a standalone tool into infrastructure that fits any stack — faster launches, more scalability, and stickier accounts.
Image & Attachment Support — Read Incoming Images + Send Images/Attachments
The problem: In the home remodeling niche (and honestly most home services), leads constantly send photos of their property or project — "here's my kitchen," "this is the bathroom we want to redo," etc. Right now the AI can't see or interpret these, which kills conversation momentum at exactly the moment the lead is most engaged. GoHighLevel's AI employee already handles this, so it's becoming table stakes. Feature request — two parts: 1. Read/analyze incoming images When a lead sends a photo, the AI should be able to analyze it and respond contextually ("Got it — looks like a galley kitchen, roughly 10x12? That's a great candidate for an open-concept remodel..."). Even basic image understanding would keep the conversation flowing naturally instead of the AI ignoring or fumbling the message. 2. Send images/attachments in conversation Let us upload a library of assets (past project photos, case studies, PDFs, brochures) that the AI can send in the right situations: Lead asks "can I see your previous work?" → AI sends 2-3 relevant project photos Lead asks about process or pricing → AI sends a case study or one-pager Follow-up sequences → ability to include images/memes, which consistently get better response rates than text-only bumps Why it matters: Visual context is core to how remodeling leads communicate. Being able to receive AND send visual content would meaningfully improve engagement, booking rates, and how human the AI feels — and it closes a gap with competitors that already offer this.
add different bot options
In ads manager, for example, you can choose what campaign structure you want to use. In appointwise, we could do the same, you can choose if bot should only answer questions, or qualify and book like its right now
Option to turn off the initial message inside appointwise
I know there is a loom tutorial on how to turn it off, but you have to do it inside GHL. It would be so much easier to just do it inside the appointwise
Seconds Delay in Follow ups
Add an option to include seconds in the message delay. That would be great option for everyone
Chat bot is organising a time but not booking it into calender?
Hey so my chat bot is organising a time with my contractor client however it is not actually booking it into the GHL calendar, how can i set it up so it books the calendar?
Advance appointment booking
I would like for the ai to be able to see further down the calendar for booking people in. I’m working with a wedding venue and people often want to see availability for viewings weeks in advance. Bit of a bottleneck in my use case
AI Generated Follow-ups
It would be great if there was an option to let the AI decide exactly what text is in the follow up with a specific lead. I find it that each lead is a different conversation and having the same exact follow up text for all of them is not convenient. GoHighLevel AI Bot has the same feature and I think it would make conversations a lot more fluid by reading the whole context and coming up with an adequate follow up.
Automated Chatbot Testing System
I would like to request a feature that allows Appointwise to automatically test chatbots and validate their behavior before launch.
Possibility to send a test AI
I would like to send the “Test AI” interface to my client, with a share button that gives me a link and gives them the possibility to try the AI (without GHL)
AI rebooking
Althoug I saw this was fixed in 7.1 I also experienced this issue. A new lead booked an appointment the agent confirmed. The conversation has been continued (this is the correct process regarding the agent setting). The lead was talked about another car model (automative) and the agent tried to book another appointment for the same time slot. It can not booked again and the lead thought his booking was lost. This is our lead ID: #2277977
Agent knowledge base extending
It would be nice to extend the available methods to create knowledge base for our agents. I think about the following: URL (web site scraping), file uploads (we have several important information stored in files). Thanks!
LInkedin integration
It would be great if we can integrate AI agents with Linkedin chats. Lead collection from Linkedin is a hot topic in our business.
Contacts Leads Dashboard summary of conversations
It would be great to see a quick AI summary of what the overall conversations were for a selected period of time. Our team has to individually go into each conversation to see what was said to each lead to ensure the bot it answering correctly.
Injecting variables from GHL
If we could inject variables from GHL so the AI can decide which route to take, we’d avoid many problems and save time by not having to create one AI per service. When leads come from forms, we already know which service they’re interested in. But with the current setup, we still need to build a conditional inside GHL to assign the right AI—when instead, Appointwise could simply read the custom field that stores the service of interest and decide the route automatically
There should be a universal Knowledge for all AI Agents
Just like in VAPI AI, if we could have one set of knowledge databases for every subaccount and link those databases to AI agents, it would save a lot of time when editing each knowledge base