The most expensive sentence in customer support may be the shortest: “It doesn’t work.” It arrives without a browser version, without the sequence of clicks, without the red error in the console, and sometimes without much patience. An agent replies with questions. The customer replies with fragments. A developer eventually opens a ticket whose principal technical detail is a feeling.
Zight makes a small wager against this ritual. Send the customer a link. They click it and record the failure in their browser. No account. No installation. Their screen comes back with browser information and, when requested, console and network logs. What was a vague complaint becomes an object that can be replayed, searched, summarized and attached to the ticket.
This is an unexpectedly grown-up job for a product that began as CloudApp, a cheerful utility whose original magic trick was putting a screenshot in the cloud and its link on your clipboard. The gesture was almost trivial: capture, paste, move on. But useful companies are often built around trivial gestures repeated millions of times. Zight says its tools now reach more than five million users.
Customer opens it in a browser.
Screen, voice and context travel together.
Logs and browser facts shrink the guessing.
AI turns the answer into a guide.
A very generic name meets a very specific problem
CloudApp had existed in various forms since 2010. In 2014 it changed hands; in 2016 Tyler Koblasa financed the acquisition of its intellectual property and brought Scott Smith into the founding team. The modern company dates itself to that year. Its intended market was broad - people designing, building, selling or supporting software - but the product action remained narrow and memorable.
The name was less helpful. “CloudApp” sounded like storage, or like a misplaced Apple product. Smith later described repeated efforts to live with the confusion, including attempted name changes and charging iOS users. None solved the basic problem. The label told people where the file went, not why the product mattered.
In April 2023, CloudApp became Zight. A coined word is harder to mistake for iCloud, but the more important change was conceptual. The company stopped presenting itself merely as a place for captures and began describing a visual work communication platform: screen recordings, screenshots, GIFs, annotations and files living together, then flowing into the software where work already happened.
“We’re big advocates of the ‘show, don’t tell’ principle at Intercom, and Zight helps us achieve that.”Geoffrey Keating, Intercom
At Intercom, one publicly described workflow starts in Dropbox Paper, moves to Slack when discussion is needed, and adds an annotated capture when words become clumsy. That is the market Zight occupies. It is not trying to replace Jira, Slack, Zendesk, Salesforce or Confluence. It supplies the missing visual noun inside them.
The recording is only the raw material
A person can record a full screen, one window, a browser tab, a camera, or screen and camera together. Microphone and system audio can travel in the same capture. Screenshots can be cropped, blurred and marked with the familiar grammar of workplace urgency: arrows, boxes, highlights. A GIF handles the tiny demonstration that does not deserve a narrated video.
When the recording stops, the product creates a share link. That speed is the old CloudApp habit, carefully preserved. The newer layer begins after capture. Zight AI transcribes in more than 50 languages, proposes a title and summary, divides a recording into chapters, and can turn it into a step-by-step guide, an SOP or a structured bug report. One-click exports can send generated material to Jira or Confluence. The video becomes searchable evidence and, sometimes, the first draft of the answer.
The sharpest extension is Request Video, because it changes who presses Record. Ordinary screen recorders explain outward: I show you my screen. A request link points inward: show me yours. For support and QA, the second direction can be more valuable. The recipient can return a recording, screenshot or large file without becoming a Zight customer. On higher tiers, the submission can carry the diagnostic material that turns “broken” into reproducible.
Four plans, one commercial ladder
Zight is conventional SaaS wrapped around an unusually quick gesture. The free Share plan covers short recordings, screenshots, GIFs and a small number of video requests. Create costs $9.95 per user per month when billed annually and removes recording limits while adding editing and a monthly allowance of AI actions. Collaborate costs $12 per user per month annually and adds team administration, branding, analytics, unlimited AI and more requests. Scale is negotiated.
The enterprise sale is not really about better arrows on screenshots. Scale adds premium integrations, SAML SSO, SCIM provisioning, group permissions, custom retention, custom S3 storage, service commitments and HIPAA support with a business associate agreement. Zight is SOC 2 Type II certified and says content is encrypted in transit and at rest on AWS-backed infrastructure. The little capture tool grew up by acquiring the controls that let a large company permit it.
Where the products lean
Loom is the obvious alternative and has the stronger video editor. Snagit goes deeper on image capture and editing. Vidyard is built around sales video and viewer analytics. Scribe and Tango specialize in procedural documentation; Jam and Birdie attack bug reports and support requests. Zight’s argument is breadth with continuity: the screenshot, recording, GIF, inbound request and AI write-up stay in one library and arrive in the tools the team already uses.
The conditions matter
Zight is less persuasive when recordings must remain entirely local, when a production-grade editor is the main requirement, or when every collaborator resists another hosted library. A simple written answer is also faster when the question is simple. Visual context is useful because some explanations are spatial and sequential - not because every sentence secretly wants to become a video.
The copyable part is smaller than it looks
Zight’s transferable lesson is not “add AI” or “integrate with everything.” It is to protect the fast original habit while expanding around the artifact it produces. Capture still needs to feel instant. The link can then collect analytics, accept comments, enter a ticket, produce a transcript and become documentation. Complexity belongs after the click, not before it.
The second lesson is to look for missing evidence. Support teams repeatedly ask customers for the same screenshots, reproduction steps and environment details. Request Video turns that scavenger hunt into a designed intake. Other companies can copy the method: identify what users fail to bring to a workflow, then make the workflow collect it automatically.
This does not work by decree. A team has to place request links where customers already are, connect the returned material to its ticket system, define access and retention, and teach agents when a recording is worth asking for. Otherwise the tool merely creates another inbox. Zight succeeds when the link travels through an existing workflow and comes back carrying enough context to remove a round of questions.
That is a modest ambition, properly understood. The company is not abolishing meetings. It is trying to make a certain class of them unnecessary: the meeting convened because one person could not see what another person saw. For that job, the little link has become surprisingly hungry.