
Questions that have an exact answer
- Limits: the largest file, the number of requests per minute, the size of a page of results.
- What happens past the limit: the error, and whether anything is saved.
- Defaults: what the system does when the customer sets nothing.
- Formats and versions that are accepted.
Find it, then check it
- Search the code for the number or the error message.
- Read the line and the few lines around it.
- Look for a second place that overrides it: a setting, a per-plan value, an environment variable.
- Only then say it.
Give the answer with its edge
An answer with the edge included ends the thread. For example: "The limit is 25 MB per file. Above that the API returns an error and nothing is stored." A bare number invites the follow-up you were trying to avoid.
When to follow up instead
- Anything about dates, roadmap or commitments.
- Security and compliance questions. These deserve a written answer from the person who owns them.
- When two places in the code disagree.
- When you could not check it. A wrong answer said with confidence costs more than a day.
After the call
Write the answer where support and sales can find it. The same question will come back next month from a different customer.