Extract actual prospect concerns, assess what the conversation supports, and draft honest follow-ups grounded in approved product facts.
No public result for version 1 yet
Version 1 · 3 variables · 3 required
Fill in the values below — the customized prompt updates as you type. marks a required value.
The offer being discussed. Default: A shared inbox for small service teams
Labeled call excerpts with both prospect and representative replies. Default: C1 Prospect: 'We cannot move all our old conversations this month.' Rep: 'It should be easy.' Prospect: 'I need to check with our office manager.' C2 Prospect: 'We only need two people to reply. Is setup going to take a full day?' Rep: 'You can start with one inbox.' No later response is included.
Verified capabilities, limits, and allowed commercial terms. Default: A team can connect one inbox for a pilot. Historical-message import is not available. No setup-time benchmark, discount, or refund policy has been supplied.
Analyze these sales-call excerpts for A shared inbox for small service teams:
C1 Prospect: 'We cannot move all our old conversations this month.' Rep: 'It should be easy.' Prospect: 'I need to check with our office manager.'
C2 Prospect: 'We only need two people to reply. Is setup going to take a full day?' Rep: 'You can start with one inbox.' No later response is included.
Approved product facts and boundaries: A team can connect one inbox for a pilot. Historical-message import is not available. No setup-time benchmark, discount, or refund policy has been supplied..
Build a table with objection category, exact prospect quote, context, the representative's response, what the prospect said next, and whether resolution is explicit or unknown. Count only distinct objections in the supplied sample; do not infer deal outcomes from polite language.
For each recurring concern, draft a better response that first acknowledges the issue, asks one useful clarifying question, and explains only a supported option. Identify concerns the offer cannot currently address. Finish with two coaching priorities and a list of product questions needing confirmation. Do not invent discounts, guarantees, competitor weaknesses, urgency, or evidence that an objection was overcome.No public examples yet for version 1
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Curated prompt only. No example output or model test is attached; model compatibility has not been verified. Default inputs are illustrative practice material; replace them with your own facts and context.
Reports go to moderators and are never shown publicly.
No public results yet
Draft an invitation that explains who the event helps, what to expect, and how to respond, while flagging missing logistics.
No public results yet
Plan a short demo with visible actions, narration, and proof of completion without inventing capabilities or results.
No public results yet
Draft a calm, specific complaint response that acknowledges the issue and stays within approved remedies and promises.
No public results yet
Separate buyer perceptions from verified product facts to produce a fair comparison brief and useful follow-up questions.
No public results yet
Create a small useful worksheet from supported expertise, with clear fields, completion checks, and a restrained offer description.
No public results yet
Identify message clarity, evidence, and next-step friction in a supplied landing page, then propose one focused alternative.
Oldest first · one level of replies
Sign in to join the discussion. Share what you learned or made with this prompt.
No comments yet
Be the first to share how this prompt worked for you.