Describe your outreach process and Makeform creates a structured log for unanswered calls, returned emails, failed visits, and other unsuccessful contact attempts. Capture who tried, when, how, what happened, and what comes next.
Send contact-attempt records to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it, or send it into the Makeform builder. Each example is a starting structure, not a completed case record.
Audience
Case workers documenting client outreach
Format
Single-attempt log with follow-up routing
Prompt size
267 chars
Example form structure
Single-attempt log with follow-up routing
Client or case reference
Attempt date, time, and staff member
How did you try to make contact?
What was the outcome?
Next action and follow-up date
Suggested routing tags
Follow-up due
Contact details need review
Escalation review
Use a separate submission for every attempt so each event keeps its own timestamp, outcome, staff member, and next-step decision.
Step 1
Identify
case reference and assigned staff member
Step 2
Record
time, method, destination, and factual outcome
Step 3
Route
follow-up date, next method, or review flag
Step 4
Repeat
a separate submission for every later attempt
Why structured attempt logs
A vague note can omit when outreach happened, which channel was used, and what comes next. A dedicated form gives staff the same factual sequence.
Each submission preserves one attempt’s staff member, time, channel, outcome, and follow-up without overwriting earlier notes.
Dropdowns distinguish no answer, unavailable voicemail, returned email, disconnected number, and no contact at a visit.
Required fields identify the next method, contact-detail check, scheduled attempt, or internal review.
Adapt to the outreach setting
Start with the closest workflow, then use your organization’s approved terminology and retention practices.
Reference, assigned worker, attempt count, next action, and supervisor review.
Approved channel, neutral-message status, and contact-detail review without clinical content.
Visit times, factual observations, notice status, and next outreach step.
Participant reference, attempt number, next method, and follow-up date.
Build the workflow
Generate the form, align it with your process, and publish it for staff.
Name permitted methods, standard outcomes, and when follow-up or review is required.
Use case references, add your channels, and write neutral factual outcomes.
Show method-specific questions and route flagged submissions to a reviewer.
Share with authorized staff and send records to your follow-up workflow.
Log vs note vs spreadsheet
Compare a quick reminder with a consistent event history across staff, channels, and dates.
Field guide
Use structured fields for filterable facts and free text for brief context. Review the form against your policies before publishing.
Record identity
Use the internal reference your team already knows. Pair it with the staff member and program without repeating unnecessary personal information.
Attempt details
Use date and time controls plus a fixed channel list. Consider a masked destination rather than repeating full contact details.
Observable outcome
Offer neutral outcomes staff can select quickly. No answer or message not delivered is clearer than guessing why someone did not respond.
Message status
Record whether an approved voicemail, card, portal message, or notice was left. A template identifier can show which wording was used.
Next action
End each record with ownership and timing: who takes the next step, which method they use, and when it is due.
Review and minimization
Flag repeated failures or details needing correction. Limit notes to relevant facts and configure access and retention to your rules.
Related tools
Connect the attempt log with intake, referral, incident, and contact-detail forms.
FAQ
Practical answers for case workers, clinic teams, and agency staff creating consistent outreach records.
It records one outreach attempt that did not result in direct contact. Each submission identifies the record and staff member, timestamps the attempt, names the method and outcome, and assigns a next action.
Include an internal reference, staff member, timestamp, attempt number, method, masked destination when needed, outcome, message status, factual note, next method, owner, and due date. Use conditional fields for channel-specific details.
Separate submissions usually create a clearer history because each attempt keeps its timestamp, channel, outcome, and author. A shared case reference connects them for sorting and review.
Use neutral outcome choices and ask for observable facts. Keep free text short, use a case reference, and remind staff not to include diagnoses, speculation, or unrelated sensitive information.
Yes. Conditional logic can ask about voicemail after phone attempts, delivery status after email, and arrival, departure, and notice status after visits.
Collect a due date, owner, next method, and review flag, then send records to your inbox, Google Sheets, Slack, or a Zapier workflow configured for your process.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses. The paid tier removes the Makeform badge. Review the form against your process before publishing.
No generic form determines requirements for every organization. Treat it as an editable starting point and have the appropriate owner review fields, access, notifications, retention, and escalation rules before use.
Replace vague outreach notes with structured events.
