Google Sheets
Log every call to a spreadsheet your team already owns - no CRM required.
Google Sheets is the zero-setup CRM. Connect it once at the workspace level, then give each agent its own call log - every call outcome (or lead) lands as a new row, ready to filter, share, or pivot on.
What it does
Once connected, Google Sheets becomes available as a post-call destination on any agent: after a call ends, oyehello reads the finished transcript and appends a row to a sheet - either logging the call outcome, creating a lead, or both. Nothing happens mid-call, so it never slows a conversation down.
You don’t need a formal CRM to get a clean, structured record of every call. If you’re already running one, Sheets works alongside it - connect both and pick whichever fits each agent.
Before you start
You’ll need:
- A Google account. Any Google account can connect and approve access - no admin setup required to get started.
- A Shared Drive, if you’re a team. Sheets created after connecting are placed in a Shared Drive folder you pick, so the sheet is owned by your organization, not by one person’s personal Google Drive. If your workspace doesn’t have a Google Workspace / Shared Drive, you can still connect - sheets just fall back to being owned by whichever personal account approved the connection.
Why this matters: a personally-owned sheet disappears from the workspace’s reach if that person ever leaves your org and their Google account is deprovisioned. A Shared Drive keeps the sheet - and every logged call - with the org.
Connect Google Sheets
- Open Integrations in the console and find the Google Sheets card.
- Click Connect Google Sheets.
- A Google popup opens - log in and approve access. You’re bounced back with a green Connected badge.
- Choose a Shared Drive folder: click Choose Shared Drive folder and pick a folder in the Google Drive picker that opens. Every sheet created from here on is placed in that folder.
If you skip the folder picker, new sheets fall back to the personal Google account that approved the connection - you can always come back and set a folder later.
Tip: if you already know a folder’s id, click Enter a folder id manually instead of using the picker. You can switch back with Choose from Google Drive instead.
Give each agent its own sheet
Connecting Google Sheets at the workspace level doesn’t log anything yet - each agent needs its own sheet, turned on individually. In an agent’s builder, under post-call actions:
- Tick Log the call outcome and/or Create a lead for Google Sheets - a “Destination sheet” panel appears.
- Pick where the rows go:
- Create a call log for this agent - provisions a brand-new spreadsheet, titled after the agent, dropped straight into your Shared Drive folder with headers already filled in. This is the default and the fastest path.
- Choose existing - opens the Google file picker so you can point at a spreadsheet you already have.
- Once set, the panel shows Sending to a Google Sheet for this agent with an Open sheet link. Click Change any time to pick a different sheet.
One sheet per agent, shared by both actions: if an agent has both “Log the call outcome” and “Create a lead” turned on for Google Sheets, they write to the same sheet - call rows and lead rows are told apart by the Type column.
What gets logged
Every row - whether it’s a call or a lead - uses the same 12-column layout, so both can live on the same tab:
| Column | Contents |
|---|---|
| Timestamp | When the call happened (ISO timestamp) |
| Type | call or lead |
| Agent | The agent’s name |
| Name | Caller’s name |
| Phone | Caller’s phone number |
| Caller’s email, if captured | |
| Company | Caller’s company (lead rows only) |
| Disposition | The call’s outcome (call rows only) |
| Notes | Call summary or lead description |
| Direction | Inbound or outbound (call rows only) |
| Duration (s) | Call length in seconds (call rows only) |
| Lead source | Where the lead came from (lead rows only) |
A call row leaves the lead-only columns (Company, Lead source) blank; a lead row leaves the call-only columns (Disposition, Direction, Duration (s)) blank. The header row is written automatically the first time a sheet is used, and is never rewritten if you rename or reorder the columns yourself.
Advanced: connect with a service account
If you’d rather not use OAuth - for example, your security team wants a dedicated, non-personal identity instead of a personal Google login - open Advanced: connect with a service account under the Google Sheets connect form. Paste in a service-account JSON key (from Google Cloud) and share your target spreadsheet with that service account’s client_email.
This path skips the folder picker and the “create a new sheet” flow - you manage the spreadsheet and sharing yourself, and point the connection at an existing spreadsheetId.
Ownership and access
- Org-owned (recommended): when you connect via OAuth and pick a Shared Drive folder, every sheet created afterward lives in that Shared Drive. It’s owned by your organization, not by an individual - so it survives offboarding. If someone who set up the connection leaves and their Google account is deactivated, the sheet and its data stay put.
- Personal-account caveat: if you connect without a Shared Drive (or the connecting account doesn’t have access to one), new sheets are owned by that person’s personal Google Drive. If they later leave and their account is deprovisioned, your workspace can lose access to the sheet and its history. For any team beyond a single founder, set up a Google Workspace Shared Drive before connecting.
Troubleshooting
- Rows are landing on the wrong tab. The connection writes to whichever tab name is stored on the connector (
Sheet1by default for a freshly created sheet). If you renamed or added tabs, use Change on the agent’s destination sheet to point at the correct one, or use Choose existing to re-pick the spreadsheet. - A sheet is owned by someone’s personal account. This happens when the connection was made without a Shared Drive folder selected. Reconnect Google Sheets in Integrations, this time choosing a Shared Drive folder, then use Change on each agent to create a fresh org-owned sheet (or move the existing spreadsheet into a Shared Drive manually from Google Drive).
- Access was revoked or the connection shows “reconnect needed.” Someone changed the Google account’s permissions, or a token expired. Go back to Integrations, open the Google Sheets card, and reconnect - your agents’ sheet assignments aren’t lost, they’ll pick back up once the connection is green again.
Next: CRM & tools -> - see how Google Sheets fits alongside your other connected integrations.