Set Sydekick's working scope
How do I choose the client, location, and skill Sydekick should use?
Sydekick always answers inside a scope. If you asked about "my reviews" and got a different location's reviews, the scope was wrong, not the question. Three controls set it: the Client and Location pickers in the top bar, the page chip above the message box, and the scope control inside the composer.
The three controls, and which one wins
Client and Location pickers
- Where
- the top bar, on every workspace page
- Sets
- which client and which location the whole app is showing
- Good for
- settling the scope once, then asking several questions
The page chip
- Where
- above the message box, named after the page you are on
- Sets
- the subject area — Listings, Reviews, Dashboard
- Good for
- asking about what is already in front of you
The composer's own scope control
- Where
- inside the message box — All clients until you choose a client or location; Add client appears only when the workspace has no clients yet
- Sets
- the client this request is about
- Good for
- a one-off question about a different client
The pickers are the ones that persist, so they are the first place to look when an answer covers the wrong business. The chip and the composer control describe the request in front of you.
The Location picker is not on Clients or Locations themselves. Those pages are the location list, so there is nothing for it to narrow.
Picking a skill
A skill is a named job your agent already knows how to do — drafting review replies, generating local post ideas, looking up a business profile. Skill in the composer lets you pick one deliberately instead of hoping your wording lands on it.
Use the picker when you want Sydekick to run one specific skill. Typing one of the phrases shown on a skill's detail page does not force that skill to run. The full list and what each skill does live under Skills in the sidebar.
The Skills library is one agency-wide list — there is no per-client version of it, so changing the client scope does not change which jobs are available.
What Sydekick remembers between conversations
Scope does one more thing: it decides which stored facts Sydekick reads. Those live under Agent → Memory, described there as "Durable facts Sydekick reads into every relevant draft."
Memory uses the same three levels. When stored facts overlap, Sydekick uses the most specific one: location first, then client, then agency. So a fact filed against one location takes precedence over a conflicting one filed against its client, and a client-level fact takes precedence over the agency-wide one.
That is what makes it useful. An agency-level note like "never promise same-day service" applies everywhere. A client-level note like "this client's brand voice is warm and informal" applies to that client's drafts. A location-level note like "this store closes at 4pm on Sundays" only affects that store. (Those three are written here as examples of the shape a memory takes — they are not memories that exist in your workspace.)
Sydekick also proposes memories on its own. They appear in a Sydekick suggested strip at the top of the Memory page with Keep and Discard on each one, and they are already influencing drafts while they sit there — so it is worth clearing that strip rather than leaving it. Add memory files one yourself against whichever scope you choose.