Personalized decks

Register a Google Slides deck as a template once, and Foyai fills it in for every buyer: their company name, logo, a summary of your last call, their stated goals and challenges, and more. Each room gets its own copy, generated automatically the moment the deck is added.

Where to find it: Content Library → Add deck template, then add the template to a room from the Add Content picker's "Deck templates" group.

Paid feature. Each deck generation uses one AI room generation from your workspace's monthly pool. See Plans and billing.

Making a template

Any Google Slides deck can become a template. Put {{tokens}} in text boxes and shapes where you want per-buyer content. Case doesn't matter, and you can use spaces or underscores: {{Company}}, {{first_name}}, and {{First Name}} all resolve to the same field.

When you add the deck (Content Library → Add deck template, picking the file from Google Drive), Foyai scans it for tokens and shows you what it found: recognized fields, and a warning for anything it didn't recognize (those are left as literal text in the generated copy; fix the spelling and re-pick to rescan).

Geometry rules

• One token per text box for anything that can run to more than a line (challenges, goals, next steps, a call summary). The inserted text does not auto-shrink to fit, so keep the box roomy enough for the field's maximum length (see the table below).
• {{logo}} alone in its own shape. Never inside a table cell or next to other text. It's replaced with an image, not text, and needs a shape of its own.
• The bullet trick. Put a multi-line token (like {{challenges}} or {{next_steps}}) inside a bulleted paragraph in Slides, and each line of the generated content renders as its own bullet. Handy for turning an AI-extracted list into a proper bulleted slide without any extra setup.
• Caps are enforced on every field: a value that runs long is trimmed (with an ellipsis) to the limits below, so a slide can never blow past the size you designed it for.

Field reference

{{logo}} is the same logo as the room header: the one you uploaded in the room's settings if there is one, otherwise the logo auto-detected from the buyer's company domain. See Buyer logo. If no logo can be found, the shape is left blank and the field is listed as missing.

CRM fields come straight from the room's linked record and the room owner's profile, with no AI involved. AI fields come from the same call-extraction Foyai already runs for AI drafts; a field with nothing to draw from (no linked deal, no calls yet) is left blank and listed as missing on the room's deck section.

Adding a template to a room

Open a room, Add content → Full-Screen Content, and pick from the Deck templates group at the top of the library tab (separate from your plain library assets). Foyai copies the template, fills every recognized token, and attaches the result as a PDF-rendered deck. Generation runs in the background, same as any AI section.

Regenerating

Every room's deck has a Regenerate action. It re-copies the template and re-fills every field with the room's current data, discarding any hand edits made to the previous copy in Google Slides. Use it after a new call lands, the linked deal changes, or you've updated the template itself.

Editing the generated deck by hand

The generated copy is a real Google Slides file. Open it from the room's Open in Google Slides link and edit it directly. Hand edits reach buyers within a few minutes, the same as any other Google-backed content in Foyai. Just remember Regenerate overwrites them.

Whose Drive the deck lands in

A template is shared across every room in your workspace, but each generated copy is made with your own Google connection and lands in your own My Drive, in a folder Foyai creates called Foyai decks. The deck belongs to the person who asked for it: you own the file, it counts against your Drive storage, and you can open, edit or delete it without anyone else's help.

Two consequences worth knowing:

• You need a Google Workspace account connected. Personal Google accounts (gmail.com and similar) are not accepted, because the sharing controls Foyai relies on are a Workspace feature.
• A colleague disconnecting Google no longer breaks your decks. Generation depends on your connection, not on whoever registered the template.

Stage automation generates a deck for the deal's owner. If no owner can be resolved, Foyai creates the deck section but leaves it unstarted rather than generating into an arbitrary colleague's Drive.

Authorizing a template

Google requires per-file permission, so the first time you generate from a given template you authorize that one file once. Until you do, the room's deck section says Waiting for your Google authorization with an Authorize button. Click it, pick the same template in the Google file picker that opens, and Foyai takes it from there.

Authorizing is per person and per template, not per room:

• It is a one-time step for that template. Every later deck you generate from it goes straight through.
• Authorizing releases every deck of yours already waiting on that template at once. When more than one is queued the button says so, for example "Authorize and generate 4 pending decks".
• If the deck is waiting on a colleague, the section names them instead ("Waiting for Dana's Google authorization") and offers no button. Google grants are personal, so only they can do it.

A waiting deck is not an error and never blocks publishing. The publish dialog lists it as a warning so you can decide whether to wait, and if you go ahead the buyer simply does not see that section until the deck is filled.

How buyers see the deck

Foyai does not create a public link to your generated deck. The copy stays private in your Drive, visible to you and nobody else, and Foyai renders it inside the room through its own access control. A buyer sees the deck because they cleared the room's gate (email verification, your domain allow-list, or a magic link), not because they hold a link to a Google file.

What that means in practice:

• Forwarding the room link does not forward the deck. Anyone who has not cleared the room's gate sees nothing, and the Google file itself asks them to sign in.
• Your Google admin's link-sharing setting no longer matters for delivery. Nothing is shared outside your organization, so there is nothing for the policy to block.
• Hand edits still reach buyers. Foyai checks the copy for changes as buyers view it and re-renders within a few minutes of an edit in Slides.
• Keep your Google connection live. The deck is rendered with your connection. If it lapses, buyers keep seeing the last rendered version while you reconnect in Settings → Integrations.

Decks generated before this change keep working exactly as they did, on the link they already have. Regenerating one moves it to the private path.

Sharing the template with your team

Keep templates in a shared drive. A template sitting in one person's My Drive is only as available as that person's account: colleagues can't open it, and if they leave the company it leaves with them. A shared drive (in Google Drive: Shared drives) belongs to the team instead, so everyone can already see the file and nothing breaks when someone changes role. Everyone who generates from a template needs to be able to open it, so this matters more now that each seller copies it with their own account.

The visibility check at registration

When you register a template, Foyai asks Google whether everyone at your Workspace domain can open the source file. If only you can, the confirmation shows a warning and a single button, Share with everyone at your-domain.com (can view). One click adds a view-only grant for your whole domain. The file stays out of colleagues' Drive search results; they reach it through Foyai. If you aren't allowed to change the file's sharing, Foyai tells you to ask its owner to do it instead.

The check is advisory and never blocks anything. Teams that share collateral through a Google Group look private to it, so a warning is a prompt to look, not a verdict. Foyai repeats the check daily and flags the template's library card with "Not shared with your org" if the sharing is removed later.

Troubleshooting

A field came up blank. CRM fields need the room linked to a CRM record (and, for seller fields, a value on the profile); AI fields need at least one analyzed call. The room's deck section lists exactly which fields were missing on the last generation.

Some tokens weren't recognized. Check the spelling against the field reference above. Recognition is case- and separator-insensitive, but the word itself has to match. Unrecognized tokens are left as literal text {{like this}} in the generated deck; fix the source template and re-pick it to rescan.

The deck says "Waiting for your Google authorization". You have not authorized this template in Google yet. Click Authorize on the section and pick the same template in the file picker. See Authorizing a template. If it names a colleague instead of you, only they can clear it.

The deck says "Sharing blocked by your Google admin". This is now rare: it only applies to decks generated before Foyai stopped creating public links, and to the occasional deck Google will not render to PDF (usually a very large one). In those cases the copy was made and filled correctly, but Google refused to give buyers a link to it, so the section stays hidden from the room. Your Workspace has link sharing outside the organization switched off. The quickest fix is to click Regenerate on the section, which moves the deck to the private path and needs no admin change at all. If you would rather keep the existing copy, ask IT to allow link sharing for your account in the Google Admin console under Drive and Docs → Sharing settings, then click Retry sharing. Retry only re-runs the sharing step, so nothing is regenerated and no AI generation is spent. The file is kept in your Drive the whole time.

The deck says it can't be loaded right now. Foyai renders the deck with the Google connection of whoever generated it, and that connection has lapsed. Reconnect Google in Settings → Integrations and the section recovers on the next view. Buyers keep seeing the last rendered version in the meantime.

Generation failed. The room's deck section shows the reason and a Retry button. Common causes: your Google connection was revoked or expired (reconnect in Settings → Integrations), or the source template was moved or deleted in Drive (re-pick it in the Content Library).

A deck landed somewhere other than my Drive. Foyai checks where each copy actually ended up and refuses to hand buyers a file you do not control. If a copy is created on a shared drive or owned by another account, Foyai deletes it and marks the section failed rather than publishing it. Authorize the template from your own account and generate again.