Postscript FAQ is a useful search because it points at a real inbox problem, not a vague productivity wish. The reader wants quick answers about how the product works.
The FAQ should answer product fit, provider support, safety, AI drafting, labels, and privacy without hype. The Postscript position is simple: AI should reduce the work, but the user should still be able to inspect the reasoning, correct the system, and approve anything that leaves the inbox.
What to look for
- Gmail and Outlook support if your work crosses both ecosystems.
- Drafts that use thread context instead of isolated prompt text.
- Labels, categories, or priority decisions that explain why they were applied.
- Tone controls that account for the sender relationship.
- Privacy settings for sensitive senders, domains, labels, and accounts.
- A workflow that defaults to review before action.
Where Postscript fits
Postscript's architecture is designed for Gmail, Outlook, review-first drafts, label reasoning, tone memory, and feedback.
What to avoid
Update this page whenever pricing, launch status, or security claims change.
FAQ
What is the best way to think about Postscript FAQ?
Start with the workflow and risk level. If a message affects a customer, candidate, manager, or business relationship, prefer AI that drafts and explains rather than AI that silently acts.
Where does Postscript fit?
Postscript is built for review-first AI email across Gmail and Outlook: draft suggestions, labels, priority, tone memory, and feedback that remain visible to the user.
Should AI send these emails automatically?
For most professional inboxes, no. Drafting and triage are useful. Sending should stay explicit unless the user has configured a narrow, trusted workflow.