Prepare a data subject request reply with identity check, scope, deadline, and systems to search.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this for an access, deletion, correction, or objection request.
Record the date received, the channel, the requester, and exactly what they asked for, quoted. Note the deadline from the company's own procedure and the date it falls on. Check identity with the method the procedure names; if the check has not passed or cannot be read, stop and say so.
List the systems from the data map that may hold this person's data, with the owner of each. For each system note:
Draft a short, plain reply that confirms the request, says what happens next, and gives the date the requester can expect an answer. For deletion, list the systems in scope and any records the procedure says must be kept, with the source of that rule. Put anything that needs a legal view in a note for counsel.
Never delete, export, or change data yourself, and do not send the reply or claim a search is complete without each owner's confirmation. This is not legal advice.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.