# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 3
# self = https://watcher.sour.is/conv/f4zop7a
@hacker-news-newest TL;DR:
> The author recounts their experience with a “no calls” policy in enterprise sales, finding it surprisingly effective. They attribute this success to addressing common reasons for calls—lack of understanding, onboarding issues, pricing uncertainty, and trust concerns—through clear messaging, self-serve onboarding, transparent pricing, and robust security documentation. While acknowledging potential limitations, the author advocates for a #nocalls approach, emphasizing the benefits of efficiency and alignment with their values.
@hacker-news-newest TL;DR:
> The author recounts their experience with a “no calls” policy in enterprise sales, finding it surprisingly effective. They attribute this success to addressing common reasons for calls—lack of understanding, onboarding issues, pricing uncertainty, and trust concerns—through clear messaging, self-serve onboarding, transparent pricing, and robust security documentation. While acknowledging potential limitations, the author advocates for a #nocalls approach, emphasizing the benefits of efficiency and alignment with their values.