Working with Quinn
For Stackpoint team members · September 2026
Start here
Open your Quinn DM in Slack and say Show me my preferences page. Review your preferences, connect Slack and optionally your phone, then try an internal meeting.
For an existing request, reply in its Slack thread. Say pause to stop Quinn's work on that request, resume to continue, or retry to check an interrupted action. Pausing does not cancel a calendar event.
I'm Quinn, Stackpoint's scheduling assistant. I'm an AI, and every message I send says so. I find meeting times on your calendar, handle the back-and-forth with the people you meet, send the invite, and move or cancel it when plans change. Matt set me up and runs me; you tell me how you like your calendar handled, and I work from that.
What I do
- Find times. I read your Stackpoint calendar (and a personal calendar, if you share one with me) and offer only times that are actually open: inside your hours, with the buffers you want, never inside a Focus block or a back-to-back run without asking you first.
- Run the back-and-forth. I propose times to the other person by email or text, read their reply, and settle on one. If none of the times work, I offer more. If they go quiet, I follow up, a few times at most.
- Book it. Once a time is agreed the invite goes out from your calendar, with you as the organizer, a video link or the address, and everyone on it. Reschedules and cancellations go through me too.
- Links you paste yourself. A booking link for a thread I'm not in (your own text or email with someone). They pick a time on a page that shows your real openings, in their timezone, and it books.
- Group meetings. Two or more outside people on one meeting get a poll: each ticks the times that work, and I book the earliest one everyone marked. You can also ask for a poll link to drop into a group chat yourself.
- Meetings with colleagues. When several Stackpoint people are on a meeting, I check everyone's calendar and honor everyone's preferences, not only yours.
- In person. Save your places ("the office", "my coffee spot") and I put the address and a map on the invite and keep travel time clear on either side.
- People by name. Say "find 30 minutes with Pat Lee" and I look Pat up in your contacts: your Stackpoint Google contacts automatically, your iPhone's address book once you connect it (I'll send a private link during setup).
- Quick questions. "What number do you have for Pat?" or "What's on my Thursday?" gets an answer, not a scheduling thread.
How to ask
Slack
DM me in plain language. Names, emails, phone numbers, how long, when, where: whatever you have. I read text only: if you attach a screenshot, type out what it shows.
Find me 30 min with Pat Lee pat@acme.com next week, video.
Give me a 45-minute link I can send Jordan.
Coffee with Sam Ortiz near the office, some morning the week of the 21st.
Move my 2pm with Acme to Thursday.
Email
Cc or forward quinn@stackpoint.com into any thread and say what you want ("Quinn, find us 30 minutes next week"). I take it from there and reply on the thread, signed as your assistant.
Text
Once your mobile number is on file with Matt, you can text me the same way you'd DM me, and I can text the people you meet with when that's the better channel.
How I check with you
- Before the first message to someone. I show you the draft in Slack and send only after you say go. Everything after that on the same thread I handle myself.
- Before cancelling on an outside person. I ask.
- Before booking into a Focus block or a run of back-to-back meetings. I ask, with the time named.
- Receipts. One line in your DM when something books, moves, or needs you.
Loosen or tighten any of this by telling me: "reply on email threads I loop you into without asking", "just cancel it, don't ask", "always show me drafts". It's saved for good.
Your preferences
Review your preferences together on a private web page. Save my contact and optionally connect your phone and contacts there. The goal is to understand and trust how I will handle your calendar before real scheduling. Ask for your preferences page to see your hours, meeting types, buffers, reminders, connected calendars and permissions in one place. You can edit everything later.
Change anything later in a sentence: "no calls before 10", "Fridays are for deep work", "use my Zoom, not Meet". Ask "what do you have for me?" to see what I've saved.
Privacy
- What you tell me stays on your threads. A teammate's Quinn can see only whether you're free or busy at a time, never what's on your calendar, your hours, your preferences, your contacts, or what you and I said.
- Contacts are read live, read-only, and never copied. Credentials you connect are stored encrypted on Stackpoint's server, used only for your own requests, and revocable by you at any time.
- Matt, as my operator, can read threads for support.
- The people I schedule with see only your name, the times, and my messages, signed as an AI assistant. Anyone can reply STOP to a text from me and I stop texting them.
The full privacy policy.
When something's off
- Tell me on the thread ("stop", "hold off", "drop this") and I stop.
- If I got a time or a person wrong, say so and I fix it; the person on the other end sees a correction from me.
- Anything I can't sort out, I bring to you rather than guess.
- For anything else: matt@stackpoint.com.
Next
Planned, from the AI OS backlog. No dates yet; ask Matt for where each stands.
- Personal Gmail contacts. Connect a personal Google account from the setup page; waiting on Google's review of the app.
- Smarter contact matching. Prefer a person's work address for work meetings when your address book has several.
- My number in my emails. Once the carrier approves it, people can text me to reschedule instead of emailing.
- In person, v2. Live travel-time estimates, place suggestions near where you already are that day, and awareness of travel blocks you added yourself.
- Group texts. Add me to a group iMessage and I post the scheduling link into the thread itself.
- Recruiting. Interview scheduling with Greenhouse as the system of record.