Qwrki runs an organisation's customers, cases, projects and finance, with AI Employees working alongside its people.
Each organisation has its own workspace. Its admins decide who works in it, which modules are on and which outside accounts are connected.
What it covers
Customers and sales
Customers, leads, deals and contracts.
Cases
Requests and issues from customers, with their notes and history.
Projects and time
Projects, tasks, milestones and the time spent on them.
Finance
Invoices, payments, expenses and credit notes.
Growth
Website, search and advertising figures, and content planning.
AI Employees
AI workers an organisation sets up, gives a job and supervises, with a person approving the emails and messages they send; live chat and call answers are not approved first.
Website Chat
An assistant on the organisation's own website that answers visitors from content the organisation chooses.
How your data is handled
The permissions Qwrki asks Google for, and the documents that cover the data, are below.
Google data Qwrki can read
An organisation's admin can connect Google Analytics, Search Console and Google Ads so the organisation sees its own figures in Qwrki. Qwrki does not access Gmail or Google Drive. If this changes, this policy will say so first. Qwrki asks Google only for the permissions below.
| Permission | Connected by | What Qwrki reads | Why |
|---|---|---|---|
| openid | An admin, for the organisation | The Google account's identifier. | So a later reconnection can only use the same Google account. |
| analytics.readonly | An admin, for the organisation | Report totals for the Google Analytics property the admin picks: sessions, users, conversions and sessions by channel. | To show the organisation its own website figures on its dashboards. |
| webmasters.readonly | An admin, for the organisation | Search Console totals for the site the admin picks: clicks, impressions and click-through rate, also split by search query, page, device and country. | To show the organisation how its site appears in Google Search. |
| adwords | An admin, for the organisation | Performance reports for the Google Ads account the admin picks: cost, clicks, impressions and conversions. Google offers no read-only Ads permission; Qwrki only reads reports and never changes a campaign. | To show the organisation its advertising figures beside its other figures. |
| openid, email | A member, for themselves | The identifier and email address of the member's own Google account. | To show which account is connected and to refuse a different account on reconnection. |
| calendar.readonly | A member, for themselves | Requested only when Qwrki has switched calendar sync on. The member's own Google Calendar: the events on the member's primary calendar for the next 24 hours, shown beside the member's meetings. Events are read each time and never stored. | So the member can see their own day when scheduling a meeting. |
| calendar.events | A member, for themselves | Requested only when Qwrki has switched calendar write on. The member's own Google Calendar: one meeting the member chooses, added to the member's own primary calendar. Adding the same meeting twice adds nothing new. Qwrki stores no copy of the event; the audit trail records the meeting id. | So the member can add a scheduled meeting to their own Google Calendar. |
Qwrki's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Read Google's policy.
How Qwrki stores, shares and deletes this data is in the privacy policy. Use of the app is covered by the terms. Setup guides.