Connected services
Connections live under Integrations: marketplaces, CRM systems, banks, mailboxes, telephony, document flow, messengers, accounting and more. Once connected, the agent can read data from them and act on your behalf.
Name the service with @
A connection does not tell the agent where the numbers should come from. Type @ and pick the service inside the request.
Build a report from @mango_office for 1–14 June for the "Support" group: total inbound, answered and missed calls; separately — called back, was called back, unreachable, spam.
If you have several accounts, say which one: "the Ozon shop, not the Wildberries one", "the legal entity that handles retail".
When there is no data
“No access” is about permissions, not attention
If the agent says it has no access, it really has none. Check that the connection is active under Integrations, that it has not expired, and that the service actually holds the data you are asking for.
Then check the brief itself: is the period named, is the group or shop named, and are you asking for data this service does not hold (cost price, for instance, usually lives in the accounting system rather than in a marketplace account).
Actions, not just reading
The agent can do more than read from connected services. It can reply to reviews and questions, create deals and contacts, send emails and messages, update prices and stock — where the connection grants those rights.
Those changes go straight into your service, so the limits of an edit belong in the request itself: how many records, under what condition and in which account. How to phrase that is covered in Changes in your services.