Record the question in concrete terms
“Asked about service” is hard to prepare for. “Asked whether the team has appointments available next week” identifies an answer someone can obtain. Preserve the substance of the question without adding unsupported interpretations such as “ready to buy.”
Keep the note relevant to the business task. You rarely need unrelated personal details to explain the answer being requested. If you are paraphrasing, make the wording clear enough that another rep can tell which detail must be confirmed.
Separate the answer from the plan to get it
Use three short lines: the question, the source of the answer and the next step. Until the answer is confirmed, label it unresolved. A plan to check availability is not availability; a plan to obtain a quote is not an agreed price.
In PixelKnock, save the note in the property’s Activity tab. If there is an actual agreed callback or appointment, save its required date and time as well. If the work is only an internal check, say so. A shared note can name the person responsible, but that does not create an automatic assignment or notification.
Use a question-to-answer example
A fictional initial note:
Question: are morning appointments available next week? Answer owner: operations. Next step: confirm actual availability before the requested Thursday callback. No appointment has been reserved.
A useful later update:
Operations confirmed the available windows. Bring those options to the scheduled discussion; the homeowner has not selected one yet.
| Stage | What belongs in the record |
|---|---|
| Question captured | Specific wording and relevant context |
| Answer being checked | Responsible person and source |
| Answer confirmed | The confirmed fact and any limits |
| Answer discussed | What was actually decided afterward |
This sequence prevents an internal answer from being mistaken for a homeowner agreement.
Close the question explicitly
After the question is answered or no longer relevant, add the result. Update the scheduled next step when needed and mark completed preparation work done where appropriate. Do not keep a stale open question on every future note merely because it was once important.
Before a handoff, ask the receiving teammate to identify the question and current answer from the saved record. If they cannot, shorten and clarify the note. PixelKnock is useful here because the question stays with the property rather than being separated across memory, messages and an unrelated task list.