From an event inquiry to a tailored proposal.
Every event brings its own date, location, guest count, and requirements. That context needs to stay with the customer as the conversation moves from a website request to a call and a quote.
What was connected
- Website inquiries → Twenty CRM
- Event details and source context enter the customer and opportunity records.
- CRM contacts → Quo business phone
- Named customer contacts sync with a link back to the CRM record.
- Proposals → delivery and viewing activity
- Approved proposals can be sent by SMS through a link on Stretch Tent’s own domain. Delivery and viewing events return to CRM for follow-up.
What the owner reports
100 leads in the first two weeks of implementation. Yaro also reports that one person can handle 20+ inquiries per day, including individually prepared quotes.
Results supplied by Yaro Korets on October 8, 2026. This is a first-party implementation, not an independent customer testimonial. Lead volume and handling capacity are reported observations; no before-and-after conversion, revenue, or ROI measurement is claimed.
Why the connection matters
The next conversation starts with the inquiry details, customer history, and proposal activity already linked. The operator can focus on the customer’s event and the commercial decision.
Proposal sending and commercial decisions retain human control. A viewed proposal is distinct from an accepted quote, a signature, or a confirmed payment.
Discuss a similar implementation