📖 How to use Reply — field-by-field instructions
▼
Reply generates a professional email reply based on an email you received. Paste the incoming email, select a tone, optionally add context, and click Generate reply. The example below uses a project delay email from an ING Bank stakeholder.
Tone
Professional — formal and structured, for clients and management. Personal — warm and relationship-first, for trusted contacts. Short & Sharp — zero filler, for when time is short. Select the one that fits the relationship.
Incoming email
Paste the full email you received here. The AI reads the entire content and crafts a reply that directly addresses what was asked. Include all original text for the best result.
Your name
Used as the sign-off name in the reply. Leave blank if you prefer to add it yourself.
Your role
Helps the AI frame your position correctly. A Project Manager reply sounds different from a Sales Executive reply — even for the same email.
Project / client
Gives the AI context about the relationship and project. E.g. ING Bank — ERP Migration. The reply will reference this where natural.
Key constraint
The most important field for risk control. Add instructions like “Do not commit to new deadlines” or “Do not discuss pricing”. The AI will respect these boundaries in the reply.
💡 Best results tip: Always fill in the Key constraint field. This is what prevents the AI from inadvertently committing you to something you didn’t intend. The more specific your constraint, the safer the reply.
ProQuenta Reply
Professional email replies, on demand.
Paste an email, choose your tone, get a precise response.
✦ Example — ING Bank project delay scenario
Professional
Formal and structured — for clients and management.
✓
Personal
Warm and relationship-first — for trusted contacts.
✓
Short & Sharp
Zero filler, pure intent — when time is short.
✓
Incoming email
697 characters
Your reply
Professional tone
📌 Example output.
Dear Sandra,
Thank you for your follow-up and for putting your questions in writing — I appreciate the clarity.
Regarding the data migration risk assessment: I confirm we will deliver a written risk assessment and mitigation plan for the two affected legacy data streams by end of this week (Friday, 5pm). This document will also include the basis for the CR-007 scope justification the committee requires.
Regarding the go-live impact if CR-007 is not approved this week: the Q4 go-live date cannot be maintained without this approval. The data cleansing work covered by CR-007 is on the critical path. A decision delay of one week translates to a minimum one-week go-live delay due to the build and testing dependencies downstream. I will include a full dependency schedule in the written document.
I will confirm receipt formally and provide both documents by Friday.
Best regards,
Jan de Vries
Project Manager — ING Bank ERP Migration