Product direction
Collect customer proof once. Use it everywhere. Reviews stay the first step, and Customer Flow stays how a finished job can produce a review, a photo, a testimonial, a referral or a mailing-list opt-in. This is direction, not a delivery schedule. Shipped work lives on the changelog.
In active development. Still subject to change.
Reply to Google reviews from Testimo, instead of copying a draft into Google. Update hours, description, and photos, and post updates or offers, without leaving the app. Profile reporting would use the performance figures Google provides.
Exploring. We're working out the right shape. Not a commitment to ship yet.
One Customer Flow currently applies to every review request. Templates for different industries and job types are the next step, with timing, conditions and follow-up you can set once. Review requests, testimonials, photos, referrals, feedback and mailing-list opt-ins would be easier to configure on each template. Exclusions, consent and duplicate checks would stop the same customer being asked twice, and completion would be easier to see. The aim is less manual work after a completed job.
ServiceM8, Simpro, Fergus and Tradify are not connected, and none of them are in development. Which one is explored first depends on customer demand and what each platform allows. The intended path is a job marked complete in that system, an event into Testimo, then the Customer Flow you have configured. Until a native connection exists, you add the customer yourself or BCC the Testimo address on a job email.
A referral can already be collected in Customer Flow, and each reward can already generate a code for staff to redeem. The next layer is a record of each referral: when it arrived, who sent it, whether it has been followed up, and how many have been captured. A notification and a short follow-up for the referred person are part of that exploration. A converted job would be counted only where Testimo already has that data.
Exploring. We're working out the right shape. Not a commitment to ship yet.
Outreach already sends one email at a time to all contacts or to people who opted into the mailing list. The copy can be written with AI, and the email sends straight away. Scheduling that send is the known gap. A later step is a visible journey: a welcome series for new opt-ins, a follow-up after a job, and a reminder when a service is due again, with delays and conditions between steps. Results would show what was sent and how it performed.
Photos, testimonials, case-study answers, a generated case study, a portfolio item and a review card can already come from the same customer. The missing piece is treating that job as one asset: collect the photos and details in Customer Flow, assemble the project, add it to the portfolio, and reuse the approved material in a social draft and an email.
Review cards already turn a Google review into a graphic you download and post yourself. Scheduling and publishing from Testimo are separate. The exploration starts with Facebook and Instagram: connect the account, draft a post from a review, testimonial or completed job, approve it, and place it on a calendar. LinkedIn and other networks depend on demand and on what each platform allows. A post would go out only after it is approved, and engagement figures would be whatever that network provides.
Under consideration. Longer-term, and only where the data already exists.
Review requests, ratings and team results are already on the dashboard. A wider view would add testimonials, photos and case studies collected, referrals captured and followed up, and email results. Social results would be added only after publishing exists. Repeat customers and enquiries would appear only where that data is already in Testimo. The figures would be counts Testimo records. Revenue, booked jobs and sales totals need data from a job system Testimo does not have.
A connected Testimo account can already be used from Grok, ChatGPT or Claude to read review stats, recent reviews and recent customers, and to send a review request. A later assistant would draft social posts from recent jobs, prepare an email from approved assets, suggest a follow-up, and summarise what changed. Sending a message or publishing a post would require approval. This stays on the current account connection.
We're early stage and genuinely listen to feature requests. Email hello@testimo.com.au or use the in-app chat.