Templafy Agent FAQ and troubleshooting

Use this article to resolve common admin questions when setting up, customizing, or rolling out Templafy Agent.

Use case

Use this article when Templafy Agent is not available to users, cannot generate expected output, or does not use the expected layouts, knowledge, or Library content.

Fast troubleshooting keeps rollout momentum high and helps users trust Templafy Agent. It also gives admins a clear path to fix the configuration areas that most directly affect adoption: access, manifest deployment, layouts, knowledge, tone of voice, and content permissions.

Users cannot see Templafy Agent

Confirm the following:

• The user is included in the Microsoft 365 deployment target group.
• The manifest has finished propagating in Microsoft 365.
• The user is signed in with the expected Microsoft 365 and Templafy accounts.
• The user is working in a supported PowerPoint environment.

For add-in deployment guidance, see How to Distribute Templafy Web Add-ins and Add-in Deployment FAQ.

Templafy Agent cannot generate slides

Templafy Agent needs access to approved presentation layouts before it can generate new slides.

Confirm the following:

• Presentation layouts are configured.
• The user has access to the layouts.
• The layouts contain clear use cases and usable placeholders.
• The user request is specific enough for the agent to choose a layout.

For layout guidance, see How to Manage Slide Layouts.

Output does not match tone of voice

Review the tone of voice configuration used by Universal Agent. Keep the guidance concise and test it with real user prompts.

• Remove conflicting tone instructions.
• Add examples of preferred wording where helpful.
• Ask users to include audience and purpose in their prompts.

For setup guidance, see Adjusting the Tone of Voice for Document Agents.

Internal knowledge is not used

Confirm that the knowledge source is connected, available, and relevant to the user's request.

• Check that the source file or source location is current.
• Use clear source names and descriptions where available.
• Test with prompts that explicitly ask for the relevant company-specific topic.
• Remove outdated or conflicting source material.

For setup guidance, see Adding a Knowledge Source.

Library content is not found

Library results depend on content quality and user permissions.

• Confirm that the content exists in the Library.
• Confirm that the user has permission to access it.
• Review names, tags, descriptions, and image metadata.
• Archive outdated content that should not be reused.

The manifest upload fails

If Microsoft 365 rejects the manifest, confirm that the correct file is being uploaded and that the add-in deployment flow is followed.

For upload and product ID guidance, see How to Distribute Templafy Web Add-ins.

When should I contact Templafy?

Contact Templafy if Templafy Agent is not available in the tenant, if the manifest cannot be obtained, if users cannot access the agent after deployment and propagation, or if expected configuration options are missing.