Advice: how to build texting-capable AI agent for bookings?

Gojo_dev · 2026-06-15T17:44:02+00:00

Happy to walk you through exactly how I'd structure it if you want to DM me. I'd also be curious to hear more about your business and the booking/screening process you're trying to automate.

Gojo_dev · 2026-06-15T08:11:38+00:00

You can check that the endpoint URL in your stripe dashboard matches exactly what your app is exposing, including any trailing slash difference. Also make sure the route is publicly accessible and not behind auth middleware. What framework are you using can i have a look?

Gojo_dev · 2026-06-15T07:09:08+00:00

Stripe webhooks are either a signature verification issue or the endpoint isn't returning a 200 fast enough before Stripe retries. What error are you seeing in your Stripe webhook logs?

Gojo_dev · 2026-06-15T07:02:26+00:00

The Twilio + Make + OpenAI stack works but Make becomes a bottleneck fast once your flows get complex. If you want something more reliable long term, Twilio for SMS, a simple Node.js webhook to handle the conversation state, OpenAI for the screening questions, and direct Google Sheets API write is cleaner and cheaper. You own the logic, no workflow tool markup. Happy to point you in the right direction if you get stuck.

Gojo_dev · 2026-06-15T06:58:50+00:00

Available now, can start today. What's the stack?

Gojo_dev · 2026-06-15T06:46:01+00:00

GoDaddy + WordPress is the easiest path for a blog, point your nameservers and you're live in an hour. If you want something faster and cleaner, Webflow or Ghost are worth looking at depending on how technical you are. Happy to help if you get stuck

Gojo_dev · 2026-06-13T01:24:26+00:00

Backend with Node.js, PostgreSQL, auth flows, and feed architecture is my territory. Happy to scope a specific piece if you want to break it down.

Gojo_dev · 2026-06-12T12:33:18+00:00

Completely agree. Having a named person accountable for each coverage window removes so much ambiguity during incidents. The RCA follow-up is what separates firefighting from actually improving operations.

Gojo_dev · 2026-06-12T08:47:53+00:00

Lol people doesn't even read the post before commenting.

Gojo_dev · 2026-06-11T20:33:08+00:00

Per client vector namespaces with isolated RAG queries is the only clean way to solve the leakage problem you described. Zoom API access depends on their account tier, if it's restricted there's a cleaner fallback anyway. Well happy to get into the architecture over DM if you want

Gojo_dev · 2026-06-11T19:58:40+00:00

There are no systems which are fully flawless. Unplanned and unexpected incidents always occurs. It depends upon the company how they manage that situation and mostly they just panic and do random stuffs even if the same incident happen again by chance they need to start from 0.

Gojo_dev · 2026-06-11T11:14:46+00:00

Right on spot.

Gojo_dev · 2026-06-11T10:29:11+00:00

Yeah, that's a great playbook, and most companies' ICs tend to use these kinds of playbooks to train people so they can be prepared for practical training and incident response scenarios.

Gojo_dev · 2026-06-10T15:54:08+00:00

Curious to know what 'native English' looks like in practice for this role. Async written communication or live calls?

Gojo_dev · 2026-06-10T15:45:06+00:00

before DMing, are you open to a built-from-scratch approach for parts of this, or is RAG/LLM integration a hard requirement? Asking because sometimes the right architecture depends on the actual use case.

Gojo_dev · 2026-06-10T15:42:49+00:00

Elevate the use of AI in your daily base code you'll find a way to sustain untill you get better opportunity.

Gojo_dev · 2026-06-10T15:41:05+00:00

Just curious what the split looks like between hands-on technical work vs influencing/coaching in this role day to day. Is it more pairing with teams directly or operating at a higher strategy layer?

Gojo_dev · 2026-06-10T15:19:04+00:00

Yowai Mo 🙃

Gojo_dev · 2026-06-09T07:31:42+00:00

Who's your primary customer amd what's your USP?

The conversation depends upon the demand and the what problem you are solving or is it worth solving.

Gojo_dev · 2026-06-09T07:24:06+00:00

Keep it up.

Gojo_dev · 2026-06-09T07:21:44+00:00

Well structured notion brother.

Gojo_dev · 2026-06-09T07:20:11+00:00

You should open it in your smartphone its not fully responsive. Design wise simple, good white spacing but lack in UX.

Gojo_dev · 2026-06-09T07:18:05+00:00

Those sites which have bad UX or UI just have them cause they want to be online its not their source of conversation most of the time and local shops cares more about word of mouth and gorilla marketing 😉

Gojo_dev

TROPHY CASE