Automated Client Feedback: A Chirply Setup Guide

Automated client feedback works when a request leads to a response someone can act on. Choose a customer milestone, collect a short private response and give follow-up a clear owner. Keep that service-improvement loop separate from the decision to publish a testimonial or request a public review.

Chirply's Reputation area provides locations, request links, SMS and email delivery, written feedback and recovery status. The practical starting point is one tested request for one location, followed by a clear process for reviewing the response. A CRM can make collection consistent; your team still needs to resolve the customer's concern.

Choose the question and the next action

Ask about a specific experience: a completed project phase, a recent service visit or a support interaction. Avoid asking customers to evaluate several unrelated experiences in one score. Decide who will review the answer before sending the first request.

Chirply's private feedback journey asks for a rating from one to five, optional written feedback and whether the customer wants the team to contact them. That gives the reviewer both a score and context. A one-to-five rating is not automatically an NPS result; do not label it as a different survey method in a report.

For the publishing side of the process, use the separate testimonial and review collection guide. It covers review invitations, permissions and video testimonial boundaries.

Set up the request in Chirply

Open Reputation and add or choose the business location. A location inside Chirply organizes your records; it does not create or verify a Google Business Profile. Attach public review destinations only when they are appropriate for that business.

Choose the location in the request form. Create review link makes a trackable link without sending a message. Use that option to inspect the journey before delivery. The link-only form can also record a customer name for internal identification.

For delivery, select SMS or email and choose an existing CRM contact with the required phone number or email address. Review the message and the connected sending setup. Text the review link and Email the review link send real messages and log them in the contact conversation. Connected-provider usage is separate from the Chirply subscription; check current plans and provider costs before activating a recurring process.

Use a team-controlled test contact for the first run. Confirm that the link opens the intended business's feedback page, the response appears in the correct workspace and the person responsible can find it. Do not use a real customer as an unannounced test recipient.

Build the milestone around a supported signal

A useful milestone might be a completed project phase or a deliberate account-manager check-in. An event in another tool is not automatically available as a Chirply trigger. Confirm the trigger or integration you actually have, and use manual enrollment for the pilot when that is the clearest reliable option.

Write down the audience, channel, request timing and stopping rule. Start with one invitation and review the response before considering a reminder. Preserve opt-outs and existing communication preferences. Having a contact's phone number does not establish permission to text them.

If a separate system needs to create a link or send a request, consult the API and MCP documentation. The create-link and send-request actions have different effects: the first creates a record; the second delivers a message through a provider. Keep that boundary explicit in an integration.

Use recovery status to close the loop

In the feedback journey, a rating of three or below, or a request for contact, marks the feedback as needing follow-up. Higher ratings can mark a response as a testimonial candidate. Those are starting points for review, not a substitute for reading the customer's comment.

The recovery form supports Needs follow-up, In progress and Resolved, with private notes. Use the notes to record what the team checked, what it agreed with the customer and what still needs doing. Updating recovery status records the internal state; it does not itself send a reply to the customer.

Set a response target your team can actually maintain. Review unowned or unresolved items regularly. Do not mark an issue resolved solely because someone sent a message: check whether the promised action happened and whether another team member needs to take over.

Keep public review access independent of the rating

After private feedback is submitted, Chirply shows configured public review options to every customer, regardless of rating. You can prioritize service recovery for a dissatisfied customer while leaving those public options available.

Do not turn the process into a filter that invites only high-scoring customers to leave public reviews. Google's review policy prohibits selectively soliciting positive reviews. Check other destinations' rules before using them in a request.

A testimonial-candidate flag also does not grant permission to publish. Confirm the exact wording, attribution and intended channels separately. Private feedback can remain useful internally even when the customer does not want to appear in marketing.

Measure the stages separately

Track requests, private responses, unresolved follow-up, verified public reviews and approved testimonials as different outcomes. Submitting the private feedback form marks the Chirply request completed. It does not prove that a public review was posted or a testimonial approved.

For a response rate, choose a clear reporting period and denominator, such as delivered invitations that were eligible for a response. Keep undelivered messages and duplicate requests visible rather than silently counting them as satisfied customers. If delivery or response matching is uncertain, state that limitation in the report.

Compare feedback across similar experiences and periods. An average from a handful of different project types can hide the specific issue an account manager needs to address. Review the written comments alongside the counts, and use a recurring team check-in to decide what to change in the service.

Run one feedback loop before expanding

Start with one location, one eligible milestone and one team-controlled test. Verify the request, response, recovery notes and public-review options. Then review one small real audience before activating delivery through the connected provider.

Explore Chirply's CRM and communication features and the current trial terms to evaluate the whole process. The trial requires a card and provider usage is billed separately. Expand only when your team can reliably collect the response and act on it.