Prompts for operations teams

Use Topolo Auth to invite [name and email] to our organization as [role]. Show me the available roles and what each can do, pick the least access that fits and confirm with me before sending the invitation.

Use Topolo Auth to list our organization roles, their permissions and the members assigned to each. Flag anyone with broader access than their role suggests and list members with no role. Recommend changes only. Do not change any access.

Use Topolo Auth to read the audit log for the last 14 days. Highlight sign-ins from new places, role or permission changes, new API keys and failed attempts. Explain what each means and which ones I should check with the person involved.

Use Topolo Consent to check our cookie and consent setup. Show the readiness status, run the cookie scanner on [site] and list the cookies it finds that are not covered. Recommend what to fix and do not change settings.

Use Topolo Consent to list open data subject requests. Show the type, requester, date received and what is needed to complete each one. Prepare the status updates for my approval and do not close any request.

Use Topolo CRM to import the lead list I am attaching. First show the import template and a preview, then report how many rows are new, how many look like duplicates of existing contacts, and which rows have missing or invalid fields. Do not run the import until I approve the preview.

Use Topolo Forms and CRM to set up an inquiry intake process for our product-design consultancy. Collect name, work email, company and a short project brief, including the information needed to qualify teams preparing to improve an existing digital product. Reuse an existing suitable form and CRM pipeline where available. Configure the supported native handoff to create or update the customer record and assign a follow-up task to the current sales owner. Check field mappings and duplicate handling, then show the form preview, CRM destination and any activation steps requiring approval.

Use Topolo CRM to review our current lead routing rules and propose a new rule that assigns inbound leads by [region or company size] to the right sales owner. Show the existing rules first, explain any overlap or gap, and prepare the new rule for my approval before creating it.

Use Topolo Support to review our current inboxes and routing rules, then propose a rule that routes [billing / technical / account] tickets to the right team member. Explain what changes for incoming tickets and test it against five recent tickets before you create it.

Use Topolo Web to run the publish preflight and the quality check on our site draft. List every error and warning, explain the three that matter most, fix the safe ones in the draft, and tell me what is still blocking publication. Do not publish.

Use Topolo Sign to prepare an envelope for the document I am attaching, with [name and email] as the signer. Check that every signature field is placed, show me the envelope before sending, and send it only after I confirm.

Use Topolo Sign to create a template from our standard [type of agreement]. Define the signer roles, mark where each person signs and fills in details, and name the template so the team can find it. Show me the template before saving.

Use Topolo Docs to create a space called [name] for our standard procedures. Add pages for the three processes I describe below, each with purpose, steps, owner and when to use it. Processes: [list them].

Use Topolo Docs to build a practical team handbook from our approved project notes for our delivery team. Organize it around the tasks people need to complete, with clear steps, responsibilities and linked source material. Identify contradictory or missing information. Save a navigable draft with an overview and task-specific pages, then return the document links and open questions for review.

Use Topolo Roadmap and Docs to write this week's update for [project]. List what was completed, what is in progress and what is blocked, using each item's actual status and comments. Highlight dates at risk and save the update in Docs with a link.

Use Topolo Docs and Roadmap to read the meeting notes titled [title]. List the decisions and action items you find, with owners and dates only where the notes state them. Create roadmap items for the actions after I approve the list and link them back to the notes.

Use Topolo Roadmap to review [roadmap name]. Check dependencies and the execution forecast, name the items most likely to slip and why, and recommend what to move or cut. Only suggest changes. Do not edit items.

Use Topolo Insights to create a dashboard for [goal]. List the events we already track, define any missing event you need, then create the dashboard with the charts I describe. Tell me which events still need instrumentation.

Use Topolo Flow to build a flow for [repeated task, for example: when a form is submitted, create a CRM contact and notify the team]. Show me the steps and the apps it touches, create it, then do one test run and show the result. Keep it off until I say go.

Use Topolo Flow to add an approval step before [action, such as sending a customer message] in the flow [flow name]. Show how the approval request appears, who can decide and what happens on reject. Test it with one sample run.

Use Topolo Agent to create a [role, such as support triage] agent. Write its purpose in plain language, show which actions and apps it should be allowed to use, and stop before granting any access so I can approve each one.

Use Topolo Inventory to list items by location with their quantity, then review recent stock movements. Flag items that look low and movements that look unusual and propose what to reorder. Do not record or approve any movement.