Monetize Spirit

The best of two brains: a seasoned entrepreneur + a young tech whiz.

Our Mission: Helping small businesses thrive with daily tips and tools we actually use.

[Monetize Spirit @RareGraceland]

𝗟𝗲𝘁𝘀 𝘁𝘂𝗿𝗻 𝘆𝗼𝘂𝗿 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿’𝘀 𝗰𝗼𝗺𝗽𝗹𝗮𝗶𝗻𝘁𝘀 𝗶𝗻𝘁𝗼 𝘆𝗼𝘂𝗿 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀𝗲𝘀 𝗻𝗲𝘄 𝘀𝗲𝗿𝘃𝗶𝗰𝗲 𝘂𝗽𝗴𝗿𝗮𝗱𝗲.

We’ll use AI to organize the feedback, then check the actual experience before deciding what to fix.

𝘈 𝘣𝘦𝘵𝘵𝘦𝘳 𝘢𝘱𝘰𝘭𝘰𝘨𝘺 𝘸𝘰𝘯’𝘵 𝘳𝘦𝘱𝘢𝘪𝘳 𝘢 𝘭𝘪𝘯𝘬 𝘵𝘩𝘢𝘵 𝘴𝘵𝘪𝘭𝘭 𝘥𝘰𝘦𝘴𝘯’𝘵 𝘸𝘰𝘳𝘬!

𝟭.) 𝗦𝘁𝗮𝗿𝘁 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿’𝘀 𝗼𝘄𝗻 𝘄𝗼𝗿𝗱𝘀.
Collect 𝟭𝟬 𝗿𝗲𝗰𝗲𝗻𝘁 𝗳𝗲𝗲𝗱𝗯𝗮𝗰𝗸 𝗺𝗲𝘀𝘀𝗮𝗴𝗲𝘀 from a defined period. Include questions and positive comments as well as complaints.

𝗞𝗲𝗲𝗽 𝗲𝗻𝗼𝘂𝗴𝗵 𝗰𝗼𝗻𝘁𝗲𝘅𝘁 to understand what happened. Use an approved business tool and remove identifying information where it isn’t needed.

“𝘐 𝘤𝘰𝘶𝘭𝘥𝘯’𝘵 𝘧𝘪𝘯𝘥 𝘵𝘩𝘦 𝘶𝘱𝘭𝘰𝘢𝘥 𝘭𝘪𝘯𝘬” tells us something we can investigate.

Replacing it with “dissatisfied with onboarding” makes the problem sound more sophisticated and much less clear.

𝟮.) 𝗔𝘀𝗸 𝗔𝗜 𝘁𝗼 𝗼𝗿𝗴𝗮𝗻𝗶𝘇𝗲, 𝗻𝗼𝘁 𝗲𝘅𝗽𝗹𝗮𝗶𝗻 𝗮𝘄𝗮𝘆, 𝘁𝗵𝗲 𝗳𝗲𝗲𝗱𝗯𝗮𝗰𝗸.

Try:
"Group these messages by the specific issue described. Keep the original wording and message number beside each group. Count distinct messages and flag possible duplicates. Separate reported facts from interpretation. Don’t assume causes or add feedback that isn’t supplied."

Review the groups against the messages.
Suppose 𝟰 𝗼𝗳 𝘁𝗵𝗲 𝟭𝟬 𝗺𝗲𝗻𝘁𝗶𝗼𝗻 difficulty finding a link. That describes this sample, not 40% of all your customers.

It gives you a reasonable place to investigate.

𝟯.) 𝗙𝗼𝗹𝗹𝗼𝘄 𝘁𝗵𝗲 𝘀𝗮𝗺𝗲 𝗽𝗮𝘁𝗵 𝘁𝗵𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿 𝘁𝗼𝗼𝗸.
Find out whether the link is missing, buried in a long message, or inaccessible without permission.

𝗧𝗵𝗼𝘀𝗲 𝗻𝗲𝗲𝗱 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁 𝗳𝗶𝘅𝗲𝘀.

I don’t want us spending an afternoon improving the wording when the folder simply won’t open!

Choose one change, assign someone to make it, and record what you expect it to improve.

𝟰.) 𝗖𝗵𝗲𝗰𝗸 𝘁𝗵𝗮𝘁 𝘀𝗼𝗺𝗲𝗼𝗻𝗲 𝗰𝗮𝗻 𝗻𝗼𝘄 𝗳𝗶𝗻𝗶𝘀𝗵 𝘁𝗵𝗲 𝗷𝗼𝗯.
Ask 𝟯 𝗽𝗲𝗼𝗽𝗹𝗲 unfamiliar with the process to try it using sample information.

Can they find the link, open it, and complete the upload without coaching?

Record where they still get stuck. Revise those parts and test again.

Then watch subsequent feedback for the same issue. A small test gives you useful information; it doesn’t establish that the problem can never recur.

Where appropriate, tell the customers who raised the issue what you investigated and what changed.

“𝘛𝘩𝘢𝘯𝘬 𝘺𝘰𝘶 𝘧𝘰𝘳 𝘺𝘰𝘶𝘳 𝘧𝘦𝘦𝘥𝘣𝘢𝘤𝘬! 𝘞𝘦 𝘤𝘩𝘦𝘤𝘬𝘦𝘥 𝘪𝘵. 𝘏𝘦𝘳𝘦’𝘴 𝘸𝘩𝘢𝘵 𝘸𝘦 𝘤𝘰𝘳𝘳𝘦𝘤𝘵𝘦𝘥.”

𝗧𝗵𝗮𝘁 𝗴𝗶𝘃𝗲𝘀 𝘆𝗼𝘂𝗿 𝗿𝗲𝘀𝗽𝗼𝗻𝘀𝗲 𝘀𝘂𝗯𝘀𝘁𝗮𝗻𝗰𝗲 𝗮𝗻𝗱 𝗹𝗲𝘁𝘀 𝘁𝗵𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿 𝘀𝗲𝗲 𝘁𝗵𝗮𝘁 𝘁𝗵𝗲𝗶𝗿 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 𝗺𝗮𝘁𝘁𝗲𝗿𝗲𝗱.

[Monetize Spirit @RareGraceland]

Happy Sunday! Fellow small startup founders, what are you using today for?
I'm relaxing, and planning for my next week💪☕️

[Monetize Spirit @RareGraceland]

𝗪𝗿𝗶𝘁𝗲 𝗰𝗹𝗲𝗮𝗿 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝘂𝗽𝗱𝗮𝘁𝗲𝘀 𝘁𝗵𝗮𝘁 𝗿𝗲𝗮𝘀𝘀𝘂𝗿𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿𝘀 𝘁𝗵𝗮𝘁 𝘆𝗼𝘂 𝗵𝗮𝘃𝗲 𝘁𝗵𝗲𝗶𝗿 𝗯𝗮𝗰𝗸, 𝘀𝗼 𝘁𝗵𝗮𝘁 𝘁𝗵𝗲𝘆 𝗱𝗼𝗻’𝘁 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗰𝗵𝗮𝘀𝗲 𝘆𝗼𝘂 𝗳𝗼𝗿 𝗮𝗻𝘀𝘄𝗲𝗿𝘀.

I’ll help you turn your project notes into a message that answers “Where do things stand?” and makes the next step clear.

We’ll use AI for the draft and confirmed facts for the substance.

𝟭.) 𝗦𝘁𝗮𝗿𝘁 𝘄𝗶𝘁𝗵 𝘄𝗵𝗮𝘁 𝗵𝗮𝘀 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗰𝗵𝗮𝗻𝗴𝗲𝗱.

Gather what is completed, what remains underway, and anything waiting on a decision.

Check uncertain details with the person doing the work.

“Nearly finished” and “finished” mean different things to someone planning around your delivery.

Keep that distinction in the update, even when the more confident version sounds nicer.

𝟮.) 𝗔𝗻𝘀𝘄𝗲𝗿 𝘁𝗵𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿’𝘀 𝗻𝗲𝘅𝘁 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀.
Organize the message around:
- What has changed since the last update?
- What happens next?
- Is anything needed from the customer?

“We’re working hard on your project” tells me you’re busy. I’d also like to know what’s happening with my project!

Include enough detail for the person to understand progress or make the next decision.

𝟯.) 𝗚𝗶𝘃𝗲 𝗔𝗜 𝗮 𝗽𝗿𝗲𝗰𝗶𝘀𝗲 𝗱𝗿𝗮𝗳𝘁𝗶𝗻𝗴 𝗷𝗼𝗯.
Try:
"Draft a customer project update of no more than 120 words. Explain completed work, the next step, and any action needed from the customer. Use only the supplied facts. Keep proposed dates separate from confirmed dates. List missing information in an internal checklist below the draft."

Resolve that checklist before sending the customer section.

Here’s a fictional example:

"Your first 2 page layouts are ready to review. The mobile adjustments are still underway. Please send your feedback through the review link by Wednesday, as agreed. Jo will use it for the next revision. Your next update is scheduled for Thursday afternoon."

Check every number, date, link, and commitment against the actual project.

𝟰.) 𝗠𝗮𝗸𝗲 𝘁𝗵𝗲 𝗻𝗲𝘅𝘁 𝘂𝗽𝗱𝗮𝘁𝗲 𝘀𝗼𝗺𝗲𝗼𝗻𝗲’𝘀 𝗿𝗲𝘀𝗽𝗼𝗻𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝘆.
Agree on a useful update rhythm with the customer and assign the person who will send it.

If progress is waiting on something, explain what is pending and what happens next. Don’t manufacture an achievement just to have something cheerful to report.

An accurate update can still be reassuring when it shows that someone knows what needs attention.

And please check that the approved message was actually sent. A lovely draft sitting in a folder isn’t keeping anyone informed!

Try this on your next 𝟯 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝘂𝗽𝗱𝗮𝘁𝗲𝘀.

Notice which questions customers still ask and whether you can answer them sooner next time.

“𝘐 𝘬𝘯𝘰𝘸 𝘸𝘩𝘦𝘳𝘦 𝘵𝘩𝘪𝘯𝘨𝘴 𝘴𝘵𝘢𝘯𝘥, 𝘢𝘯𝘥 𝘐 𝘬𝘯𝘰𝘸 𝘸𝘩𝘢𝘵 𝘩𝘢𝘱𝘱𝘦𝘯𝘴 𝘯𝘦𝘹𝘵.”

𝙏𝙝𝙖𝙩’𝙨 𝙩𝙝𝙚 𝙘𝙤𝙣𝙛𝙞𝙙𝙚𝙣𝙘𝙚 𝙬𝙚’𝙧𝙚 𝙝𝙚𝙡𝙥𝙞𝙣𝙜 𝙮𝙤𝙪 𝙜𝙞𝙫𝙚 𝙩𝙝𝙚𝙢.

[Arnav Sharma @arnavshr09]

One week of learning HighLevel in public, with the real numbers.

Posts: 11. Quote tweets: 18. Replies: about 15. Followers: 10.

Best post: the 3 things you need before the 3 blocks of missed-call text-back. 25 views, 2 replies. The posts that ended on a question got answers. Most of the rest didn't.

Built: missed-call text-back, then 2 fixes on top of it. Broke: it texted my own test calls.

Next week: A2P registration, so the texts can actually reach US numbers.

Nothing here is impressive yet. That's why I'm writing it down.

[Monetize Spirit @RareGraceland]

@arnavshr09 Cheers, keep moving brother! We're at the A2P registration step rn, heads up they're going to want a functional website in order to accept the application

[Monetize Spirit @RareGraceland]

Ok, quote of the week right here!🙌

[Codie Sanchez @Codie_Sanchez]

You need to become addicted to finishing what you started.

[Monetize Spirit @RareGraceland]

@HeyYoGB I’ve saved a ton of time which lets me use it to make money, so yes!

[Monetize Spirit @RareGraceland]

@arnavshr09 We’re working on getting A2P registration done so we can get moving with leads - what you’re saying is very true.

[Monetize Spirit @RareGraceland]

If you’re just starting out with AI, this is a great practice to start with to build your experience.

I’d add that Day 1’s practice with prompting is 100% something to do with every single prompt you write.

The more specific and detailed the prompt, the better the output!

[Will | AI Automations @WillyTheWizardX]

You can learn the basics of AI in a week with 1 hour a day.

Prompts, summaries, writing, research, spreadsheets, one automation, then a review.

The full 7 day plan is below (screenshot it).

[Monetize Spirit @RareGraceland]

𝗟𝗲𝘁𝘀 𝘁𝘂𝗿𝗻 𝘆𝗼𝘂𝗿 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿’𝘀 𝗰𝗼𝗺𝗽𝗹𝗮𝗶𝗻𝘁𝘀 𝗶𝗻𝘁𝗼 𝘆𝗼𝘂𝗿 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀𝗲𝘀 𝗻𝗲𝘄 𝘀𝗲𝗿𝘃𝗶𝗰𝗲 𝘂𝗽𝗴𝗿𝗮𝗱𝗲.

We’ll use AI to organize the feedback, then check the actual experience before deciding what to fix.

𝘈 𝘣𝘦𝘵𝘵𝘦𝘳 𝘢𝘱𝘰𝘭𝘰𝘨𝘺 𝘸𝘰𝘯’𝘵 𝘳𝘦𝘱𝘢𝘪𝘳 𝘢 𝘭𝘪𝘯𝘬 𝘵𝘩𝘢𝘵 𝘴𝘵𝘪𝘭𝘭 𝘥𝘰𝘦𝘴𝘯’𝘵 𝘸𝘰𝘳𝘬!

𝟭.) 𝗦𝘁𝗮𝗿𝘁 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿’𝘀 𝗼𝘄𝗻 𝘄𝗼𝗿𝗱𝘀.
Collect 𝟭𝟬 𝗿𝗲𝗰𝗲𝗻𝘁 𝗳𝗲𝗲𝗱𝗯𝗮𝗰𝗸 𝗺𝗲𝘀𝘀𝗮𝗴𝗲𝘀 from a defined period. Include questions and positive comments as well as complaints.

𝗞𝗲𝗲𝗽 𝗲𝗻𝗼𝘂𝗴𝗵 𝗰𝗼𝗻𝘁𝗲𝘅𝘁 to understand what happened. Use an approved business tool and remove identifying information where it isn’t needed.

“𝘐 𝘤𝘰𝘶𝘭𝘥𝘯’𝘵 𝘧𝘪𝘯𝘥 𝘵𝘩𝘦 𝘶𝘱𝘭𝘰𝘢𝘥 𝘭𝘪𝘯𝘬” tells us something we can investigate.

Replacing it with “dissatisfied with onboarding” makes the problem sound more sophisticated and much less clear.

𝟮.) 𝗔𝘀𝗸 𝗔𝗜 𝘁𝗼 𝗼𝗿𝗴𝗮𝗻𝗶𝘇𝗲, 𝗻𝗼𝘁 𝗲𝘅𝗽𝗹𝗮𝗶𝗻 𝗮𝘄𝗮𝘆, 𝘁𝗵𝗲 𝗳𝗲𝗲𝗱𝗯𝗮𝗰𝗸.

Try:
"Group these messages by the specific issue described. Keep the original wording and message number beside each group. Count distinct messages and flag possible duplicates. Separate reported facts from interpretation. Don’t assume causes or add feedback that isn’t supplied."

Review the groups against the messages.
Suppose 𝟰 𝗼𝗳 𝘁𝗵𝗲 𝟭𝟬 𝗺𝗲𝗻𝘁𝗶𝗼𝗻 difficulty finding a link. That describes this sample, not 40% of all your customers.

It gives you a reasonable place to investigate.

𝟯.) 𝗙𝗼𝗹𝗹𝗼𝘄 𝘁𝗵𝗲 𝘀𝗮𝗺𝗲 𝗽𝗮𝘁𝗵 𝘁𝗵𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿 𝘁𝗼𝗼𝗸.
Find out whether the link is missing, buried in a long message, or inaccessible without permission.

𝗧𝗵𝗼𝘀𝗲 𝗻𝗲𝗲𝗱 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁 𝗳𝗶𝘅𝗲𝘀.

I don’t want us spending an afternoon improving the wording when the folder simply won’t open!

Choose one change, assign someone to make it, and record what you expect it to improve.

𝟰.) 𝗖𝗵𝗲𝗰𝗸 𝘁𝗵𝗮𝘁 𝘀𝗼𝗺𝗲𝗼𝗻𝗲 𝗰𝗮𝗻 𝗻𝗼𝘄 𝗳𝗶𝗻𝗶𝘀𝗵 𝘁𝗵𝗲 𝗷𝗼𝗯.
Ask 𝟯 𝗽𝗲𝗼𝗽𝗹𝗲 unfamiliar with the process to try it using sample information.

Can they find the link, open it, and complete the upload without coaching?

Record where they still get stuck. Revise those parts and test again.

Then watch subsequent feedback for the same issue. A small test gives you useful information; it doesn’t establish that the problem can never recur.

Where appropriate, tell the customers who raised the issue what you investigated and what changed.

“𝘛𝘩𝘢𝘯𝘬 𝘺𝘰𝘶 𝘧𝘰𝘳 𝘺𝘰𝘶𝘳 𝘧𝘦𝘦𝘥𝘣𝘢𝘤𝘬! 𝘞𝘦 𝘤𝘩𝘦𝘤𝘬𝘦𝘥 𝘪𝘵. 𝘏𝘦𝘳𝘦’𝘴 𝘸𝘩𝘢𝘵 𝘸𝘦 𝘤𝘰𝘳𝘳𝘦𝘤𝘵𝘦𝘥.”

𝗧𝗵𝗮𝘁 𝗴𝗶𝘃𝗲𝘀 𝘆𝗼𝘂𝗿 𝗿𝗲𝘀𝗽𝗼𝗻𝘀𝗲 𝘀𝘂𝗯𝘀𝘁𝗮𝗻𝗰𝗲 𝗮𝗻𝗱 𝗹𝗲𝘁𝘀 𝘁𝗵𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿 𝘀𝗲𝗲 𝘁𝗵𝗮𝘁 𝘁𝗵𝗲𝗶𝗿 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 𝗺𝗮𝘁𝘁𝗲𝗿𝗲𝗱.

[Monetize Spirit @RareGraceland]

𝗪𝗿𝗶𝘁𝗲 𝗰𝗹𝗲𝗮𝗿 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝘂𝗽𝗱𝗮𝘁𝗲𝘀 𝘁𝗵𝗮𝘁 𝗿𝗲𝗮𝘀𝘀𝘂𝗿𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿𝘀 𝘁𝗵𝗮𝘁 𝘆𝗼𝘂 𝗵𝗮𝘃𝗲 𝘁𝗵𝗲𝗶𝗿 𝗯𝗮𝗰𝗸, 𝘀𝗼 𝘁𝗵𝗮𝘁 𝘁𝗵𝗲𝘆 𝗱𝗼𝗻’𝘁 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗰𝗵𝗮𝘀𝗲 𝘆𝗼𝘂 𝗳𝗼𝗿 𝗮𝗻𝘀𝘄𝗲𝗿𝘀.

I’ll help you turn your project notes into a message that answers “Where do things stand?” and makes the next step clear.

We’ll use AI for the draft and confirmed facts for the substance.

𝟭.) 𝗦𝘁𝗮𝗿𝘁 𝘄𝗶𝘁𝗵 𝘄𝗵𝗮𝘁 𝗵𝗮𝘀 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗰𝗵𝗮𝗻𝗴𝗲𝗱.

Gather what is completed, what remains underway, and anything waiting on a decision.

Check uncertain details with the person doing the work.

“Nearly finished” and “finished” mean different things to someone planning around your delivery.

Keep that distinction in the update, even when the more confident version sounds nicer.

𝟮.) 𝗔𝗻𝘀𝘄𝗲𝗿 𝘁𝗵𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿’𝘀 𝗻𝗲𝘅𝘁 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀.
Organize the message around:
- What has changed since the last update?
- What happens next?
- Is anything needed from the customer?

“We’re working hard on your project” tells me you’re busy. I’d also like to know what’s happening with my project!

Include enough detail for the person to understand progress or make the next decision.

𝟯.) 𝗚𝗶𝘃𝗲 𝗔𝗜 𝗮 𝗽𝗿𝗲𝗰𝗶𝘀𝗲 𝗱𝗿𝗮𝗳𝘁𝗶𝗻𝗴 𝗷𝗼𝗯.
Try:
"Draft a customer project update of no more than 120 words. Explain completed work, the next step, and any action needed from the customer. Use only the supplied facts. Keep proposed dates separate from confirmed dates. List missing information in an internal checklist below the draft."

Resolve that checklist before sending the customer section.

Here’s a fictional example:

"Your first 2 page layouts are ready to review. The mobile adjustments are still underway. Please send your feedback through the review link by Wednesday, as agreed. Jo will use it for the next revision. Your next update is scheduled for Thursday afternoon."

Check every number, date, link, and commitment against the actual project.

𝟰.) 𝗠𝗮𝗸𝗲 𝘁𝗵𝗲 𝗻𝗲𝘅𝘁 𝘂𝗽𝗱𝗮𝘁𝗲 𝘀𝗼𝗺𝗲𝗼𝗻𝗲’𝘀 𝗿𝗲𝘀𝗽𝗼𝗻𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝘆.
Agree on a useful update rhythm with the customer and assign the person who will send it.

If progress is waiting on something, explain what is pending and what happens next. Don’t manufacture an achievement just to have something cheerful to report.

An accurate update can still be reassuring when it shows that someone knows what needs attention.

And please check that the approved message was actually sent. A lovely draft sitting in a folder isn’t keeping anyone informed!

Try this on your next 𝟯 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝘂𝗽𝗱𝗮𝘁𝗲𝘀.

Notice which questions customers still ask and whether you can answer them sooner next time.

“𝘐 𝘬𝘯𝘰𝘸 𝘸𝘩𝘦𝘳𝘦 𝘵𝘩𝘪𝘯𝘨𝘴 𝘴𝘵𝘢𝘯𝘥, 𝘢𝘯𝘥 𝘐 𝘬𝘯𝘰𝘸 𝘸𝘩𝘢𝘵 𝘩𝘢𝘱𝘱𝘦𝘯𝘴 𝘯𝘦𝘹𝘵.”

𝙏𝙝𝙖𝙩’𝙨 𝙩𝙝𝙚 𝙘𝙤𝙣𝙛𝙞𝙙𝙚𝙣𝙘𝙚 𝙬𝙚’𝙧𝙚 𝙝𝙚𝙡𝙥𝙞𝙣𝙜 𝙮𝙤𝙪 𝙜𝙞𝙫𝙚 𝙩𝙝𝙚𝙢.

[Monetize Spirit @RareGraceland]

@arnavshr09 Here's to the consistent action! 🍻

[Arnav Sharma @arnavshr09]

Day 7. HighLevel shipped a new workflow action this week, Add Internal Comment. Added it to my missed-call text-back.

Now when the text goes out, the workflow also drops a private note on the conversation: missed call, text sent, waiting on a reply.

Took 9 minutes. Most of that was getting the caller's number and the call time into the comment with custom values.

Tested it with 3 calls. All 3 notes showed up in Conversations, visible only to the team.

Small thing, but whoever calls back now knows what already happened before they dial.

What would you put in that note?

[Monetize Spirit @RareGraceland]

Entrepreneurship doesn't start when you know everything.

Entrepreneurship starts with DOING and learning as you go!

[Monetize Spirit @RareGraceland]

You don't need to understand every AI tool before you start using AI.

𝗦𝘁𝗮𝗿𝘁𝗶𝗻𝗴 𝗮𝗻𝗱 𝗿𝗲𝗳𝗶𝗻𝗶𝗻𝗴 𝗶𝘀 𝗯𝗲𝘁𝘁𝗲𝗿 than 𝙬𝙖𝙞𝙩𝙞𝙣𝙜 for perfection.

[Monetize Spirit @RareGraceland]

𝗟𝗲𝘁’𝘀 𝗴𝗲𝘁 𝘆𝗼𝘂 𝗿𝗲𝗮𝗱𝘆 𝘁𝗼 𝗻𝗮𝗶𝗹 𝘁𝗵𝗲 𝘀𝗮𝗹𝗲𝘀 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻 𝘆𝗼𝘂’𝘃𝗲 𝗯𝗲𝗲𝗻 𝗵𝗼𝗽𝗶𝗻𝗴 𝗻𝗼𝗯𝗼𝗱𝘆 𝗮𝘀𝗸𝘀.

I’ll show you how to use AI to practice answering a customer’s concern fully so its resolved and they feel confident to move forward with you.

For this exercise, the customer says:
“We tried automation once. It created more work.”

𝘛𝘩𝘢𝘵 𝘥𝘦𝘴𝘦𝘳𝘷𝘦𝘴 𝘢 𝘳𝘦𝘢𝘭 𝘤𝘰𝘯𝘷𝘦𝘳𝘴𝘢𝘵𝘪𝘰𝘯.

𝟭.) 𝗚𝗶𝘃𝗲 𝘁𝗵𝗲 𝗿𝗲𝗵𝗲𝗮𝗿𝘀𝗮𝗹 𝘆𝗼𝘂𝗿 𝗿𝗲𝗹𝗲𝘃𝗮𝗻𝘁 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗱𝗲𝘁𝗮𝗶𝗹𝘀 𝘁𝗼 𝘄𝗼𝗿𝗸 𝘄𝗶𝘁𝗵.

Supply your actual offer, what it includes, its limits, and the prices you’re ready to discuss.

Use a fictional buyer situation rather than private customer information.

In our example, the buyer runs a small service business and is concerned about setup and maintenance.

We’re practicing how to understand that concern and explain the relevant help.

𝟮.) 𝗔𝘀𝗸 𝗔𝗜 𝘁𝗼 𝗽𝗹𝗮𝘆 𝘁𝗵𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿 𝗼𝗻𝗲 𝗲𝘅𝗰𝗵𝗮𝗻𝗴𝗲 𝗮𝘁 𝗮 𝘁𝗶𝗺𝗲.
Try:
"Role-play a prospective customer in the situation below. Start with the stated concern. Respond to one message at a time and don’t automatically agree with me.

After 5 exchanges, stop. Review whether I understood the concern, explained the offer accurately, and proposed an appropriate next step. Flag promises unsupported by the offer details."

Respond as you would in a real conversation.
Don’t aim for a perfect paragraph. Practice finding out what the person needs to know.

𝟯.) 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱 𝘄𝗵𝗮𝘁 𝗵𝗮𝗽𝗽𝗲𝗻𝗲𝗱 𝗯𝗲𝗳𝗼𝗿𝗲 𝗲𝘅𝗽𝗹𝗮𝗶𝗻𝗶𝗻𝗴 𝘆𝗼𝘂𝗿 𝘀𝗼𝗹𝘂𝘁𝗶𝗼𝗻.

A useful first question could be:
“Which part created the extra work: setting it up, keeping it running, or correcting what it produced?”

𝙇𝙚𝙩 𝙩𝙝𝙚 𝙖𝙣𝙨𝙬𝙚𝙧 𝙜𝙪𝙞𝙙𝙚 𝙮𝙤𝙪.

Then check your understanding:
“𝗦𝗼 𝘆𝗼𝘂𝗿 𝗺𝗮𝗶𝗻 𝗰𝗼𝗻𝗰𝗲𝗿𝗻 𝗶𝘀 𝘄𝗵𝗼 𝗺𝗮𝗶𝗻𝘁𝗮𝗶𝗻𝘀 𝗶𝘁 𝗮𝗳𝘁𝗲𝗿 𝘀𝗲𝘁𝘂𝗽. 𝗛𝗮𝘃𝗲 𝗜 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗼𝗼𝗱 𝘁𝗵𝗮𝘁?”

Now you have a particular concern to address using the actual terms of your offer.

I wouldn’t want to give someone a beautiful explanation of faster setup when they’re worried about six months of maintenance!

𝟰.) 𝗥𝗲𝘃𝗶𝗲𝘄 𝗵𝗼𝘄 𝘄𝗲𝗹𝗹 𝘆𝗼𝘂 𝗵𝗲𝗹𝗽𝗲𝗱 𝘁𝗵𝗲𝗺 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱.
Look for 𝟯 𝘁𝗵𝗶𝗻𝗴𝘀:

Did you understand the concern before recommending anything?

Did you explain the relevant help without adding promises?

Did the next step fit their situation?

Read the exchange yourself. Treat the AI’s feedback as something to consider, not a verdict on your ability.

Try another round with a different concern, such as timing or whether the service fits the job.

A chatbot agreeing to buy isn’t the result we’re measuring.

The useful result is being better prepared to listen, explain, and help a real customer.

[John Zhao | TikTok Shop from 0 @JohnZhaoLog]

Making a sale on TikTok Shop and getting paid for it happen weeks apart...

Commission isn't released when someone buys. From a few creator payout breakdowns, it gets confirmed after the order is delivered and the return window closes. Settlement is usually around 15 days and can stretch to 31 during policy or security checks (check the current timing in your own affiliate dashboard, it changes)

What that means if you're starting:

- Pending and settled show up separately in your dashboard. Pending isn't money yet, so don't count it

- Returns cancel the commission on that order. TikTok Shop also just added box-free returns at around 10,000 US drop-off spots, so keep an eye on your return rate

- Expect a gap between your first sale and your first payout. That part is normal

[Monetize Spirit @RareGraceland]

@winnerbiology Simplify life and you'll succeed.

[Monetize Spirit @RareGraceland]

𝗟𝗲𝘁’𝘀 𝗴𝗲𝘁 𝘆𝗼𝘂 𝗿𝗲𝗮𝗱𝘆 𝘁𝗼 𝗻𝗮𝗶𝗹 𝘁𝗵𝗲 𝘀𝗮𝗹𝗲𝘀 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻 𝘆𝗼𝘂’𝘃𝗲 𝗯𝗲𝗲𝗻 𝗵𝗼𝗽𝗶𝗻𝗴 𝗻𝗼𝗯𝗼𝗱𝘆 𝗮𝘀𝗸𝘀.

I’ll show you how to use AI to practice answering a customer’s concern fully so its resolved and they feel confident to move forward with you.

For this exercise, the customer says:
“We tried automation once. It created more work.”

𝘛𝘩𝘢𝘵 𝘥𝘦𝘴𝘦𝘳𝘷𝘦𝘴 𝘢 𝘳𝘦𝘢𝘭 𝘤𝘰𝘯𝘷𝘦𝘳𝘴𝘢𝘵𝘪𝘰𝘯.

𝟭.) 𝗚𝗶𝘃𝗲 𝘁𝗵𝗲 𝗿𝗲𝗵𝗲𝗮𝗿𝘀𝗮𝗹 𝘆𝗼𝘂𝗿 𝗿𝗲𝗹𝗲𝘃𝗮𝗻𝘁 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗱𝗲𝘁𝗮𝗶𝗹𝘀 𝘁𝗼 𝘄𝗼𝗿𝗸 𝘄𝗶𝘁𝗵.

Supply your actual offer, what it includes, its limits, and the prices you’re ready to discuss.

Use a fictional buyer situation rather than private customer information.

In our example, the buyer runs a small service business and is concerned about setup and maintenance.

We’re practicing how to understand that concern and explain the relevant help.

𝟮.) 𝗔𝘀𝗸 𝗔𝗜 𝘁𝗼 𝗽𝗹𝗮𝘆 𝘁𝗵𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿 𝗼𝗻𝗲 𝗲𝘅𝗰𝗵𝗮𝗻𝗴𝗲 𝗮𝘁 𝗮 𝘁𝗶𝗺𝗲.
Try:
"Role-play a prospective customer in the situation below. Start with the stated concern. Respond to one message at a time and don’t automatically agree with me.

After 5 exchanges, stop. Review whether I understood the concern, explained the offer accurately, and proposed an appropriate next step. Flag promises unsupported by the offer details."

Respond as you would in a real conversation.
Don’t aim for a perfect paragraph. Practice finding out what the person needs to know.

𝟯.) 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱 𝘄𝗵𝗮𝘁 𝗵𝗮𝗽𝗽𝗲𝗻𝗲𝗱 𝗯𝗲𝗳𝗼𝗿𝗲 𝗲𝘅𝗽𝗹𝗮𝗶𝗻𝗶𝗻𝗴 𝘆𝗼𝘂𝗿 𝘀𝗼𝗹𝘂𝘁𝗶𝗼𝗻.

A useful first question could be:
“Which part created the extra work: setting it up, keeping it running, or correcting what it produced?”

𝙇𝙚𝙩 𝙩𝙝𝙚 𝙖𝙣𝙨𝙬𝙚𝙧 𝙜𝙪𝙞𝙙𝙚 𝙮𝙤𝙪.

Then check your understanding:
“𝗦𝗼 𝘆𝗼𝘂𝗿 𝗺𝗮𝗶𝗻 𝗰𝗼𝗻𝗰𝗲𝗿𝗻 𝗶𝘀 𝘄𝗵𝗼 𝗺𝗮𝗶𝗻𝘁𝗮𝗶𝗻𝘀 𝗶𝘁 𝗮𝗳𝘁𝗲𝗿 𝘀𝗲𝘁𝘂𝗽. 𝗛𝗮𝘃𝗲 𝗜 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗼𝗼𝗱 𝘁𝗵𝗮𝘁?”

Now you have a particular concern to address using the actual terms of your offer.

I wouldn’t want to give someone a beautiful explanation of faster setup when they’re worried about six months of maintenance!

𝟰.) 𝗥𝗲𝘃𝗶𝗲𝘄 𝗵𝗼𝘄 𝘄𝗲𝗹𝗹 𝘆𝗼𝘂 𝗵𝗲𝗹𝗽𝗲𝗱 𝘁𝗵𝗲𝗺 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱.
Look for 𝟯 𝘁𝗵𝗶𝗻𝗴𝘀:

Did you understand the concern before recommending anything?

Did you explain the relevant help without adding promises?

Did the next step fit their situation?

Read the exchange yourself. Treat the AI’s feedback as something to consider, not a verdict on your ability.

Try another round with a different concern, such as timing or whether the service fits the job.

A chatbot agreeing to buy isn’t the result we’re measuring.

The useful result is being better prepared to listen, explain, and help a real customer.

[Monetize Spirit @RareGraceland]

𝗔𝗜 𝗰𝗮𝗻 𝗵𝗲𝗹𝗽 𝘆𝗼𝘂 𝗿𝗲𝘀𝗽𝗼𝗻𝗱 𝗳𝗮𝘀𝘁𝗲𝗿.
But speed alone doesn't earn a customer's trust.
That's where human attention to detail is everything.