Resending Inspections

How to resend inspections

These actions all follow the same general pattern. You send a PUT request to a /text endpoint for an existing inspection, and Vision sends the corresponding message using the inspection's configured send methods (text, email, or both).

Each action uses specific fields from the inspection type's Message Template Set. For example, requesting more uses request_more and request_more_subject, while resending the original request uses new_request and new_request_subject.

You can trigger reminder-to-start and reminder-to-finish messages manually through these endpoints, but most teams define a reminder schedule at the team level instead. To send these automatically, set auto_reminder_duration or auto_finish_reminder_duration on the team.

This page focuses on when to use each endpoint. If you need to change the message content itself, update the corresponding fields in the Message Template Sets page or in the Vision Dashboard.

Available /text actions

Request more data

Use PUT /text/request when you need additional photos, videos, or answers on an existing inspection. Any additional data stays on the same inspection record.

This action uses the request_more template field for the message body and request_more_subject for the email subject.

For the full workflow, including marking specific list items as incomplete and adding a custom message, see Request More.

Try it in the API Reference: Text > Send a request for more photos/videos via text/email.

Resend the original inspection request

Use PUT /text/welcome when you need to send the original inspection request again. This is most common after you update the customer's phone number or email address.

This action uses the new_request template field for the message body and new_request_subject for the email subject.

Try it in the API Reference: Text > Send the original inspection request via text/email.

Send a reminder to start

Use PUT /text/reminder when the customer has not started the inspection and you want to prompt them to begin. This sends the reminder-to-start message through the inspection's configured send methods.

This action uses the request_reminder template field for the message body and request_reminder_subject for the email subject.

Most teams automate this reminder by setting auto_reminder_duration on the team. Use this endpoint when you need to send that reminder manually for a specific inspection.

Try it in the API Reference: Text > Send a reminder to start the inspection via text/email.

Send a reminder to finish

Use PUT /text/reminder-to-finish when the customer has already started the inspection but has not completed it. This sends a follow-up message so they can return and finish the inspection.

This action uses the finish_reminder template field for the message body and finish_reminder_subject for the email subject.

Most teams automate this reminder by setting auto_finish_reminder_duration on the team. Use this endpoint when you need to send that reminder manually for a specific inspection.

Try it in the API Reference: Text > Send a reminder to finish the inspection via text/email.