Here are strategies for getting the most value from Workbench.
Write effective prompts
Good prompts lead to better results. Here are some strategies:
Be specific: "Check the status of this access request, verify the approvals are complete, and suggest next steps for fulfillment" is more useful than "help me with this request."
Provide context: If Workbench needs background to help you, include it. "I'm troubleshooting a failed onboarding workflow. Here's the error from the provisioning story…" will get you further than just pasting the error.
Break down complex requests: For multi-step tasks, either break them into clear steps yourself or ask Workbench to create a plan first.
Use examples: If you want output in a specific format, show an example: "Generate a report like this: [example]."
Iterate: If the first response isn't quite right, refine your request: "That's close, but can you also include…"
Use custom instructions for consistent context
As covered in the Workbench conversations module, custom instructions give Workbench persistent context across all your conversations. Review and update them as your work changes to keep Workbench's responses relevant.
Use presets to reduce setup for your team
Well-designed presets reduce individual setup time and keep tool configurations consistent across your team. If you're a team admin, create presets that match your team's common workflows.
Leverage internal tools for complex tasks
Use Think when you have a complex, multi-step request. You can explicitly ask Workbench to "think through" a problem before acting.
Use Code analyst for data analysis, calculations, or visualizations. Ask Workbench to "analyze this data and create a chart" or "calculate statistics for this dataset."
Use Formulas docs when you need accurate, current information about Tines formulas.
💡Note
Let Workbench memory work for you
Workbench memory retains context from your previous conversations, so you don't need to repeat background information each time you start a new chat. If you've previously mentioned your role, tools, or preferences, Workbench can draw on that context in future conversations.
Security considerations
Always keep security in mind when using Workbench:
Credential access: Only enable credentials for services you actually need. Review credential access regularly.
Confirmation requirements: Require confirmation for tools that make major changes, access sensitive data, or have significant cost implications.
Audit logs: Remember that all Workbench activity is logged (where available; see the Audit and compliance section). Review audit logs periodically to ensure Workbench is being used appropriately.
Data sensitivity: While Workbench keeps data within your tenant, be mindful of what information you include in conversations, especially if chat retention is long-term.