Notifications and Caity by phone

Phone numbers

In your account, Phone numbers: add a mobile number (Australian numbers can start with 04; others need their country code) and enter the 6-digit code we text you. A verified number belongs to one account. Your primary number gets texts and calls; turn texts and calls off per number.

Two-step sign-in by text: after your password, we text a code to your primary number. Passkeys don't need it. Turning it on or off asks for a code too, and removing your last verified number turns it off. An authenticator app works without a phone signal.

What reaches you, and where

In your account, Notifications:

• Inbox: the last 90 days. Alerts that escalate (a text, then a call) stop once you acknowledge them: here, by replying ACK to the text, or by answering the call.
• Channels per event: in app, push, email, text, call. Events: a sign-in from a new device, deployments failed or live, domains verified or failed, issues assigned to you, mentions, SLA breaches, unanswered invitations, meetings about to start, mail from your VIP senders, agent jobs finished or failed, and production alarms (platform administrators).
• Quiet hours: no texts or calls in your night, in your time zone. Urgent events (new-device sign-ins, SLA breaches, alarms) can still reach you if you allow it.
• VIP senders: addresses or @domains; their mail is its own event.
• Push: each phone app gets its own notifications (Tasks gets task updates, Maps gets flight alerts); the all-in-one app gets those of apps not installed on the same phone, and its inbox shows everything. Devices that receive push lists them; sign an app out under Devices to stop them.
• Calendar reminders: an invitation you haven't answered is chased as the event approaches (within twice its own reminder time, between an hour and a day before), and meetings remind you a few minutes before.

Reply STOP to our texts to stop them (sign-in codes you ask for still arrive); START to resume.

Notification protocols

Owners and admins define protocols: reusable policies an organization attaches to the whole organization or to Serverless App Services, Tasks spaces, calendars, mailboxes and agents. A rule names events, optional conditions (for example, only production deployments), steps (channels now, then more channels after some minutes while nobody has acknowledged), extra people by role, and whether it ignores quiet hours. Start from a template: production on-call (text, then a call after 5 minutes), meeting guard, invitation chaser, VIP mail, service desk SLA, agent jobs. Change a protocol once and everything it's attached to follows. Manage them under Notifications → Manage protocols, or through the API.

Caity by phone

Text or call the platform's number from your verified phone, and Caity answers as you, in the organizations you choose, with at most the permissions you set for each (never more than your role there allows):

• “What's on today?”: meetings, invitations waiting for an answer, unread mail from VIPs, issues assigned to you, failed deployments.
• “Decline the 3pm, propose Thursday at 2.”
• “Read me the important mail”, “reply to Ada: running late”, “snooze that until tomorrow at 9.”
• “Create a bug in WEB: sign-in fails on Safari”, “move WEB-12 to done.”
• “Did the deploy go out?”, “roll production back.”
• “Check grocery prices for postcode 3000” (a job on your self-hosted agent).
• “What did we decide about pricing?”, “note: call the accountant Monday” (Notes).
• By text: “call me.”

Anything that changes something or reaches other people waits for you: by text, reply YES with the code it sends; on a call, say yes when it reads the action back. You can also ask for a PIN on calls before anything changes. After a call, a summary and the transcript are saved to Notes (or Tasks) as you choose, and you can continue in Caity. Every action is in the audit log of the organization it happened in, as “you (Caity)”.

More than one organization

Turn on each organization you want Caity to act in, and choose what it may do there. Optionally pick a default organization.

• Say which one when it matters: “in Acme, create a bug…”, or “switch to Acme”. The rest of the call or text conversation stays there.
• A request that doesn't say goes to your default. Without a default, it goes to your only organization, or Caity asks: “Which organization — Acme or Globex?” Your answer holds for the rest of the conversation.
• Lists and searches (“what's on today?”, “any failed deploys?”) cover every organization you turned on and say which one each item is in. Acting on an item happens in its organization.
• An alert's call starts in the alert's organization.

Set it up in your account under Caity by phone.