Set Sydekick's working scope
How do I choose the client, location, and skill Sydekick should use?
Sydekick answers inside a scope: a client, optionally narrowed to some of its locations or tags. Set it for the conversation with the Scope button under the message box, or type # and pick a client, location or tag. If you asked about "my reviews" and got another location's, the scope was wrong, not the question.
Two other things travel with your message and are easy to mix up with scope: the page you are on (the chip above the message box, plus whatever client and location the top bar has selected) and the workspace you are signed in to. Only the Scope control sets what the conversation is about.
Key facts
| Sets the conversation's scope | The Scope button in the composer, or # in the message box |
| Starts as | All clients. A new conversation is not scoped until you scope it |
| Rule | One client per conversation. Locations and tags of that client can be added |
| Page chip and top bar | Context sent with each message. They do not set the conversation's scope |
| Choosing a skill | The Skill button or / pins one skill for the next message only |
| Skills per client | Skills, with a client selected in the top bar, has an on/off switch per skill for that client |
The three things that shape an answer
The conversation's scope
- Where
- the Scope button in the composer, or # in the message box
- Sets
- the client, and optionally the locations or tags, the conversation is about
- Good for
- keeping a whole conversation on one business
The page context
- Where
- the chip above the message box, named after the page you are on, plus the client and location selected in the top bar
- Sets
- a hint about where you are when you send. Remove the chip with its × to stop sending it
- Good for
- asking about what is already in front of you
The workspace
- Where
- the workspace you are signed in to
- Sets
- which account's clients and conversations you are in at all
- Good for
- agencies that belong to more than one workspace
Changing the Client or Location in the top bar does not set a conversation's scope. A new conversation starts at All clients, and the top bar's choice is only passed along as page context. That is why the screenshot above shows a top bar pointing at one client while the composer is unscoped.
The top bar's choice is remembered in your browser as you move around Synup, so it can be left over from earlier work. If an answer covers the wrong business, check the composer's scope first, then the top bar.
Steps
Open Sydekick from Home, the top bar or full screen. See starting a conversation.
Select Scope under the message box. On a new conversation it opens a searchable list starting at All clients. Pick a client, then All locations or one location. The list shows each location's address, and the arrow beside the client's name goes back to the client list.
Or type # in the message box. The menu lists CLIENTS, LOCATIONS, TAGS; keep typing to filter, use the arrow keys, and press Enter to pick one. The menu reminds you that there is One client per conversation. Locations and tags stay in scope.
Pick more locations or tags of the same client the same way. The composer shows one chip for the whole scope, such as Harbor & Pine Dental · 2 locations. Remove the chip with its × to go back to All clients.
Send your request. The scope you set stays with that conversation and is restored when you reopen it from the list.
Changing the client halfway through
A conversation is about one client. If you pick a different client in a conversation that already has messages, Synup keeps the earlier messages and records the change in the transcript with a line such as Scope changed to Cedar Row Coffee.
Once Sydekick has answered, it asks first: Change conversation scope says that the conversation is scoped to the first client and everything above was answered for it, and offers Start a new conversation, Switch scope here or Cancel. Start a new conversation when you want clean context. A scope change is refused while a turn is still running: wait for it to finish.
Picking a skill
A skill is a named job your agent knows how to do, such as drafting review replies or planning posts. Select Skill in the composer, or type /, to choose one deliberately instead of leaving it to your wording. A chosen skill applies to the next message only and shows as a chip you can remove with Don't run this skill.
Typing a phrase from a skill's detail page does not force that skill; only the picker does. The full list is under Skills in the left navigation. The Skill button only appears when the agent can list its skills; if it is missing, reload later.
Choosing which skills a client can use
Under Skills, with a client selected in the top bar, each skill has a switch, Available to this client. Without a client selected there are no switches, because the list describes the agency as a whole. Skills marked Always on, such as guardrails and preferences, have no switch.
How the switches behave:
- Nothing set means everything is available. A client only becomes restricted once you switch skills off, and switching every skill off is remembered as a deliberate choice rather than going back to everything.
- Skills installed for every client only widen a client's list once that client is restricted. They do not restrict a client you have not curated.
- The scope decides which list applies. With All clients in scope, no client list is applied.
- The composer's Skill list is the whole agency list, whatever the client. Whether Sydekick uses a skill you pinned that the scoped client has switched off has not been confirmed, so switch it on for the client first.
What Sydekick remembers between conversations
Scope also decides which saved memory Sydekick reads. Memory is kept under Agent → Memory at three levels, agency, client and location. When memories conflict, Sydekick is told that the more specific one wins: location, then client, then agency.
Location memory is only read when a single location is in scope, or when your message names exactly one location of the client. With several locations in scope, the client's and the agency's memory still apply. To have one store's memory used, scope the conversation to that location.
What you'll see when it's done
- A scope chip in the composer showing the client and how many locations are in scope
- The scope remembered when you reopen the conversation
- A Scope changed to … line wherever the client changed in the transcript
- Always on skills without switches, and a switch per skill for the selected client
Watch out for
- The top bar is not the scope. Selecting a client there changes what the page shows and the context Sydekick receives, not the conversation's scope.
- Do not reuse a conversation for a second client. Start a new one, so earlier answers about the first client do not colour the second.
- Some actions need a location. If Sydekick says to choose a location, pick one in the Scope control and try again.
- Check different workspaces. If you belong to more than one workspace, Sydekick will not send when the page and the open conversation belong to different workspaces, and asks you to return to the one you intended. Your message stays in the box.
Questions people ask
Why did Sydekick answer about the wrong location?
Check the scope chip under the message box first. A conversation that was never scoped answers across All clients. Then check the top bar's selection and the page chip, which are sent as context.
Does choosing a client in the top bar scope Sydekick?
No. It is passed along as page context, and removing the page chip stops that. Use Scope or # to set the conversation's scope.
Why is the Skill button missing?
It only appears when the agent can list its skills. If the list cannot be loaded, the button is hidden, and you can still send a message without pinning a skill. Reload later to get the button back.
Can I scope a conversation to several clients?
No. A conversation has one client. Add several locations or tags of that client, or start another conversation for the second client.
What is "Add your first client" in the Scope list?
It appears only when the workspace has no clients yet, and opens the form to add one. The word may read business or brand if your workspace names them that way.