How we handle GDPR data-subject requests on a deadline
Legal
An agent we run on Kortix — connected to the inbound questionnaire and our knowledge base of vetted answers and policies. It parses each question, drafts responses in the vendor's format, and flags anything it can't answer confidently.

Security questionnaires arrive in the middle of a sales cycle and hold the deal up until they're answered. The questions are mostly ones we've answered before — about our encryption, access controls, data handling, and policies — but they come in different formats each time, a SIG one deal, a CAIQ the next, a custom spreadsheet after that, and each has to be filled out in its own layout.
We run an agent on Kortix that drafts the answers from our vetted knowledge base. This is how we answer our own security questionnaires, including the connections and guardrails involved.
Most of a questionnaire is answers we already have. The same questions about encryption at rest, SSO, incident response, and data retention come up on nearly every one, and we've written vetted answers for them. But each questionnaire uses a different format, so someone has to read every question, find the matching approved answer, and paste it into the vendor's own layout — a SIG workbook, a CAIQ, or a custom spreadsheet.
The common fixes are incomplete. A shared answer library still needs a person to match each question to it by hand. Copying last deal's responses risks pulling an answer that no longer fits. A generic AI drafter with no grounding will write confident answers that aren't the vetted ones, which is exactly what can't happen on a security document.
On Kortix, each inbound questionnaire triggers an agent. It spawns an isolated session (a cloud sandbox) with access to our knowledge base of vetted answers and policy docs. It parses each question, matches it to our approved answers and policies, drafts responses in the vendor's own format — SIG, CAIQ, or a custom spreadsheet — and flags anything it can't answer confidently for a human. It returns a filled draft for security to review before it goes back.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the questionnaire skill and the 15-minute trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a security questionnaire agent in this workspace.
Create the agent agents/security-questionnaire.md. Its job is to draft responses to inbound security questionnaires from our vetted answers. It may use the Gmail, Google Drive and Google Sheets connectors.
Create the skill skills/questionnaire-response/SKILL.md with these rules:
Add a cron trigger questionnaire-check to kortix.yaml. It runs the security-questionnaire agent every 15 minutes with the prompt "Load the questionnaire-response skill and draft a response for every new questionnaire in the Security Questionnaires label."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect the inbox where questionnaires arrive and the files they come in. Credentials are brokered server-side and never enter the agent's machine.

Reads each new questionnaire and its attached files.


Supplies approved answers when the library lives there.
Posts the completed draft and its flags for security review.
Merge the change request, then start a session with the security-questionnaire agent and send this prompt. Check the drafted answers and the flagged rows before you let the schedule take over.
Draft a response to the oldest questionnaire in the Security Questionnaires label in Gmail that has no draft reply yet.
The change request added this trigger to kortix.yaml. From now on the agent
checks the label every 15 minutes, and each questionnaire runs in a new session
on its own cloud computer. To change the interval, edit the cron line, or open
Triggers in the workspace.
triggers:- slug: questionnaire-check name: Security questionnaire check on: cron: "0 */15 * * * *" run: agent: security-questionnaire prompt: Load the questionnaire-response skill and draft a response for every new questionnaire in the Security Questionnaires label.The agent drafts and flags. It never sends. The filled file waits as a Gmail draft on the original thread, and a person from security answers the flagged questions and sends it. A question with no vetted answer is left for a person, never answered from scratch.
Each run ends with one message in #security. This is what a run looks like in the session:
Drafted 1 new CAIQ questionnaire: 187 of 196 questions answered from the vetted set. 9 questions are flagged for security, mostly on subprocessors. The draft is saved on the original thread and not sent.
Once it works, paste any of these into the same session.
When security answers a flagged question, add the approved answer to memory/security-answers.md in a change request.
On the first Monday of each month, list the answers in memory/security-answers.md that no questionnaire used in the last 90 days.
If a questionnaire email names a due date, put it at the top of the #security post and remind #security two days before it.
The agent drafts a security document from our own vetted answers, so the access is scoped and contained:
Inbound questionnaires now come back as filled drafts in whatever format they arrived, with each answer drawn from our vetted knowledge base and the uncertain ones flagged. Security spends its time reviewing and answering the hard questions rather than matching and pasting, and nothing goes back to a prospect without a person's sign-off.