Let your Talent nudge you, and turn it down
Set how often your Talent may start a conversation, pick where it reaches you, and get a ping when a long run finishes.
Your Talent does not only answer. It can notice something in your connected mail or calendar and message you first. You control how often that happens and where it lands.
Set your proactivity pace
Open Home, go to Manage, then the proactivity setting. You get three controls:
- On or off. Off means your Talent never starts a conversation. It still answers you normally.
- Reach me via. Which channel a nudge arrives on.
- Pace. How many nudges a day you are willing to accept.
The pace is a hard daily cap, counted per person per local calendar day:
| Pace | Nudges per day |
|---|---|
| Off | none |
| Quiet | 1 |
| Normal (default) | 2 |
| Eager | 5 |
These are ceilings, not targets. On a quiet week you will get fewer, or none.
Quiet hours are built in. Between 10pm and 7am in your local time, your Talent does not send proactive messages at all, whatever your pace.
What it actually watches
Nudges come from what you have connected, not from guesswork. Your Talent watches the head of your connected mailboxes and your connected calendars, up to five of each, and looks for things you committed to that are about to matter.
It also will not nudge you twice about the same thing. A given subject is deduplicated for three days, so a stubborn unanswered email does not become a daily complaint.
A worked example
You are on Normal pace with Telegram as your channel. Google Calendar and Gmail are connected. On Wednesday morning you get one message:
You have the Acme QBR at 2pm and their last email asked for updated usage numbers, which nobody has sent. Want me to pull them and draft the reply?
You answer "yes". That is your one useful interruption for the day. Nothing else arrives.
Get pinged when a long run finishes
Separately from nudges, you can ask the browser to notify you when a turn is done. In the chat header there is a bell. Click it, allow notifications when your browser asks, and that device gets a push when a run finishes.
This is per device and per browser. Turning it on at your desk does not turn it on for your laptop.
The header bell is not history
The bell in the console header is a bounded inbox of things that still need you: approvals waiting, requested changes, comments on work you shared, and low credit warnings. Items leave it when they are resolved.
It is not a log. For the full record of what ran, use Activity in Settings.
What to check
- You get no nudges at all. Check the pace is not Off, check the chosen channel is still connected, and remember that quiet hours cover 10pm to 7am locally.
- You get too many. Drop from Eager to Normal or Quiet. If a specific topic keeps coming back, tell your Talent it is handled and it will stop treating it as open.
- The bell button in the chat header is missing. Your browser does not support push notifications. Safari on older versions and some in app browsers are the usual cases.
- The bell shows as blocked. You previously denied notifications for this site. TalentOS cannot re-ask. Allow notifications for the site in your browser settings, then toggle it again.
- Notifications work on one machine but not another. That is expected. Turn it on again on the second device.