Replies
Drafted for you, sent by you.
When someone asks in Gmail or Slack when you're free, Kernel checks your calendar and drafts the answer beside the request. Edit it if you like, then press Send. Nothing goes out without you.
- Thu 9th 1:30 pm ET / 10:30 am PT: free
Highlights
Times from your calendar
Kernel works out free and busy from your calendar and Hours. The model only words the greeting and closing, so a draft never states a time Kernel didn't check.
Only after you press Send
Nothing is posted automatically. Send queues one message with a ten-second Undo, then it goes out as you in the same Gmail or Slack thread.
Both zones, every time
Every time a reply states carries its zone, and both zones when the person asking is elsewhere, so 10:30 PT is never read as 10:30 ET.
Open questions
Open questions get your free times.
Asked when you're free next week, Kernel offers free times from the scheduling link you chose for availability replies and adds its booking URL. With no link, it lists free times from your Hours.
- Offered times follow the link's own slots, notice, and buffers
- Choose the link under Availability replies use
- Slack replies post in the thread, or at the top of a direct message
- Mon 13th 10:00 am ET – 12:00 pm ET
- Tue 14th 2:00 pm ET – 4:30 pm ET
- Wed 15th 9:00 am ET – 11:00 am ET
Safe sending
If your calendar moves, the draft waits.
Kernel checks your calendar again before a reply goes out. If a time was booked since the draft, the card says what changed and won't send until you regenerate it.
- Regenerate redrafts from your current calendar
- A send Kernel can't confirm is never posted again on its own
- Answering the conversation yourself closes the card
- Thu 9th 1:30 pm ET: busy
- Thu 9th 3:00 pm ET – 4:30 pm ET
- Fri 10th 10:00 am ET – 12:00 pm ET
Good to know
- Availability questions are the only replies Kernel drafts, and only in Gmail and Slack.
- A Gmail reply goes to the sender and the original To and Cc, minus you, and stays editable.
- A connection without send permission offers Copy reply instead of Send.
- If a send can't be confirmed, Kernel asks you to check the thread rather than posting twice.
- Gmail sending uses the separate Connect Gmail authorization, not your Google sign-in.