Ask Ping is good at three different jobs that look similar from the outside but go through very different paths under the hood: looking up a meeting you remember, finding a meeting by something that was said inside it, and pulling together a picture across many meetings or clients at once. Phrasing your question with the right cues makes it faster and more accurate.

When to just type and when to pin with @

Most of the time, just type your question in plain language. Ask Ping is good at figuring out which client, contact, or meeting you mean from natural cues like a name, a date, or a topic.

Use the @ mention when you want to be explicit. Picking a specific client or meeting from the @ menu pins it so Ask Ping skips the "which one did you mean" step and goes straight to the source. That's worth doing when:

  • You're asking about a specific older meeting that isn't in your recent activity
  • The person's name is common and you want to avoid disambiguation
  • You're working through a series of questions about the same client and want every answer scoped to them

Looking up a meeting you already know

If you remember roughly which meeting you mean, by title, date, attendee, or just "the tax meeting last week", ask in plain language. Ask Ping will either pull it up directly or, if several recent meetings match, show you a short list of clickable options.

A few things to know about this path. Ask Ping looks at your recent meetings here, not your whole history, so it's fast. If the meeting you mean is older or has a distinctive title, pin it with @ from the chat input and Ask Ping will load it directly without asking you to pick from a list.

Finding a meeting by what was said inside it

When you don't remember which meeting it was but you do remember the topic, the decision, or a quote, ask by content. Ask Ping searches across the inside of your meetings, not just titles and participants.

Examples of questions that route this way:

  • "Which meeting did we talk about the Section 174 changes"
  • "Where did Lauren bring up the cost segregation study"
  • "When did we agree to move the Q3 review to October"

This works because Ask Ping does semantic search over your transcripts. You don't have to use the exact words that were said. A paraphrase or a topic is enough.

Asking about a person

For questions about a specific person (what they said, what they care about, what's outstanding for them, what their role is), name them. Ask Ping resolves the person first and then pulls from their meetings, emails, and client profile.

Some examples:

  • "What did Maria say about the IRS audit timing"
  • "What's outstanding for David"
  • "What did we promise Camden on the W-2 corrections"

If the name is ambiguous and several people match, Ask Ping will show a clickable picker. Selecting one is faster than retyping.

Synthesis across multiple meetings or clients

For roll-ups, audits, and cross-source summaries, ask one wide question instead of breaking it into small ones. Ask Ping reads from meetings, emails, action items, and client profiles in parallel and assembles a structured answer.

Questions that work well here:

  • "Summarize what's outstanding for Acme this quarter"
  • "What follow-ups did I promise across my meetings this week"
  • "Build me an action item list from the Q3 onboarding calls"
  • "Compare what each prospect from last month said about pricing"

A wider question reads more context and produces a better synthesis than three narrow ones in a row.

Refining the answer

After Ask Ping answers, keep going in the same chat instead of starting over. Ask Ping holds the conversation context and can iterate without re-doing the lookup.

  • "Shorter, bullets only"
  • "Drop the section about onboarding"
  • "Rewrite in my own voice"
  • "Add the dates"

The instructions don't need to be precise. Plain language works.

Phrasing a question that lands the first time

Three cues help Ask Ping the most:

  • Who. Name the person or client if there is one. If you're asking about yourself, "I" and "me" work.
  • What kind of thing. Words like "meeting", "email", "draft", "action item", "summary" route Ask Ping to the right source.
  • Shape of the output. "A list", "two sentences", "in my voice", "with dates" tell Ask Ping what you want back.

You don't need all three. Often one is enough. But the more cues you give, the less Ask Ping has to guess.

What Ask Ping can't do on the read side

Ask Ping can only read what is stored in Ping. A few corollaries:

  • If a meeting wasn't recorded, there is no transcript for Ask Ping to read.
  • Ask Ping doesn't see your inbox unless your email is connected. Once it is, Ask Ping can search the emails Ping has indexed.
  • Ask Ping can answer about your clients, contacts, meetings, emails, action items, and Anchor services and agreements.
  • Right now Ask Ping cannot agentically query other connected platforms or integrations. If a platform is queryable through Ask Ping, it will be called out in the documentation for that integration.

If a question keeps not working the way you expect, send the example to [email protected]. It's the fastest way to make Ask Ping better at the kinds of questions you actually ask.