Ruby Appears in 83.4% of AI Answers. Here's Our Five-Step Plan to Improve Its AI Visibility.
This report supports CiteWorks Studio's examination of how AI search is recommending Virtual Receptionist Services. For more detail, you can also read Virtual Receptionist Services: AI Visibility Discovery Index.
On this report
Browse sections
- Answer Capsule
- Current AI visibility
- What changed since last month
- Next Step
- Step 1. Measure
- Step 2. Make the website consistent
- Step 3. Align the external narrative
- Step 4. Optimize priority company pages
- Step 5. Publish around buyer questions
- Our 90-day action plan
- Methodology
- Our first three priorities
- Related research
- Learn More
Key Takeaways
- Ruby is mentioned in most benchmark answers and is recommended in just over half, showing strong visibility but room to improve endorsement.
- The main opportunity is not more mentions; it is making the case for recommendation clearer in AI answers.
- Several pricing claims need verification against primary sources before any website edits or correction requests are made.
- The plan focuses on priority company pages, cited third-party pages, and buyer questions that already appear in captured answers.
Answer Capsule
In November 2026, Ruby appeared in 306 of 367 AI answers included in the Virtual Receptionist Services benchmark (83.38%). It received 195 recommendations (53.13%), with 175 Top 3 placements and 78 first-place recommendations. A mention means the company appeared in an answer; a recommendation means the answer affirmatively endorsed it.
Our plan compares the company with its competitors, checks conflicting AI claims against reliable sources, and identifies website pages, third-party sources and buyer questions to address. This edition establishes a research baseline. It does not claim a change from earlier editions measured on a different basis. Conflicting AI claims require verification before corrections are proposed.
Current AI visibility
Questions This Section Answers
- How do Ruby mentions, recommendations and placements compare with its Virtual Receptionist Services peers?
Ruby recorded 306 mentions (83.38%) and 195 recommendations (53.13%) across 367 answers included in the benchmark. Top 3 placements numbered 175; first-place recommendations numbered 78. Framing among its mentions was 201 positive, 105 neutral and 0 negative.
Rank | Company | Mentions | Mention rate | Recommendations | Recommendation rate | Top 3 | Top 3 rate | #1 | #1 rate |
|---|---|---|---|---|---|---|---|---|---|
1 | Smith.ai | 304 | 82.83% | 199 | 54.22% | 151 | 41.14% | 59 | 16.08% |
2 | Ruby | 306 | 83.38% | 195 | 53.13% | 175 | 47.68% | 78 | 21.25% |
3 | AnswerConnect | 167 | 45.50% | 130 | 35.42% | 91 | 24.80% | 24 | 6.54% |
4 | PATLive | 134 | 36.51% | 98 | 26.70% | 60 | 16.35% | 12 | 3.27% |
5 | Abby Connect | 92 | 25.07% | 65 | 17.71% | 41 | 11.17% | 3 | 0.82% |
6 | Davinci Virtual | 44 | 11.99% | 32 | 8.72% | 15 | 4.09% | 3 | 0.82% |
7 | Moneypenny | 48 | 13.08% | 29 | 7.90% | 15 | 4.09% | 5 | 1.36% |
8 | Posh Virtual Receptionists | 37 | 10.08% | 16 | 4.36% | 9 | 2.45% | 3 | 0.82% |
9 | Nexa | 23 | 6.27% | 14 | 3.81% | 7 | 1.91% | 0 | 0.00% |
10 | Conversational | 2 | 0.54% | 0 | 0.00% | 0 | 0.00% | 0 | 0.00% |
Ruby appears in nearly every benchmark answer and is endorsed in a little over half of them, which puts it at the top of the field alongside Smith.ai. The gap between appearing and being recommended is the practical opportunity: Ruby is seen often but is not always the answer an assistant puts forward.
Placement is a separate strength. Ruby's shortlist and first-place showings are strong relative to its recommendation share, so the work is less about earning attention than about making the case for endorsement clearer. We would build a scorecard that tracks mentions, recommendations and placements as distinct measures so the client can see where the gap sits.
Framing is almost entirely positive or neutral, with no negative mentions recorded. That is a useful foundation, but positive wording alone does not equal a recommendation, so we would not treat sentiment as a proxy for endorsement.
What changed since last month
Questions This Section Answers
- How did Ruby counts and coverage differ across the available monthly snapshots?
Metric | Nov 2026 |
|---|---|
Mentions | 306 / 367 (83.38%) |
Recommendations | 195 / 367 (53.13%) |
Top 3 recommendations | 175 / 367 (47.68%) |
#1 recommendations | 78 / 367 (21.25%) |
Only months with verified results are shown. Monthly sample coverage is listed in Methodology.
This edition establishes a broader research baseline. Earlier editions used a narrower set of questions, so their figures are not treated as a performance trend.
This edition sets a broader baseline than the earlier reports, which used a narrower set of questions. The current figures should be read as a starting point for future comparison rather than as a movement from prior months.
Because the question set changed, a different answer total does not tell us why counts or rates moved. We would describe the observed results and the comparability limit separately, and avoid drawing a trend line across editions that were not measured the same way.
Future editions using this screening scope can be compared against this baseline. Until then, the client should treat the current numbers as a reference point, not a verdict on recent performance.
AI recommendation trend
Observed recommendation rate (%), Nov 2026
- Rubyno changeNov 202653.13%
Separate selected monthly samples. Missing points are unavailable, not zero. Provider/prompt equivalence is unverified; rate movement does not demonstrate causation.
/ Take the next step
Want to Understand Your AI Citation Footprint?
We start every engagement with a full audit of how AI systems reference your brand today.
Measurable, Repeatable Programme
Build a durable foundation of credible citations that compounds over time and continues to influence AI answers as new queries emerge
Citation Architecture Review
Identify which high-authority community sources are and aren't working in your favour across AI platforms.
AI Visibility Audit
Understand exactly how LLMs are referencing your brand today and which sources are shaping those answers.
Step 1. Measure
Questions This Section Answers
- What should the agency measure and verify first for Ruby?
AI answers contained 8 conflicting claims about Ruby: 0 critical, 1 high, 5 medium, 2 low. Of these, 1 was rated critical or high priority; the critical claims are included in that total. These ratings help prioritize fact-checking. They do not establish that a company or publisher made an error.
The benchmark recorded a small set of conflicting claims about Ruby, most of them medium severity and only one rated high. These ratings are a prioritization tool for fact-checking, not evidence that any company or publisher made an error.
A visibility comparison alongside a scoped list of claims to check would let the client decide where verification effort is worth spending first. We would separate claims that affect pricing perception from those that are merely inconsistent, since pricing conflicts are the ones most likely to shape a buyer's expectations.
The output would be a fact-review register with an owner and an evidence requirement for each item, so the client can confirm, correct or set aside each claim on the record.
Step 2. Make the website consistent
Questions This Section Answers
- Which recorded claim differences about Ruby should be verified before proposed page edits?
Review topic | Severity | Recorded AI claim A | Recorded AI claim B |
|---|---|---|---|
monthly price | medium | ~$250/month | $250/mo for 100 minutes |
monthly price for 50 minutes | low | $250/month for 50 minutes | $269/month for 50 minutes |
starting monthly price | medium | ~$235/month | ~$250/month |
monthly price for 50-minute plan | high | $250/month for 50 minutes | $135-$700+ for 50-500 minutes (implies ~$135 for 50 minutes) |
Both columns quote AI answers, not verified company facts. Resolve the entity, date and source before deciding whether a correction is warranted; different dates can explain an apparent conflict.
The disputed topics cluster around monthly pricing, including the cost of a smaller plan and the starting price. Both columns in the review table quote AI answers, not verified company facts, so neither can be treated as correct until checked.
Different dates or plan definitions can explain an apparent conflict, so the first step is to resolve the entity, the date and the source behind each figure. We would not decide which claim is true from the benchmark alone.
Once the client confirms current pricing from primary sources, we would prepare conditional page briefs for the pricing pages, written to answer the specific questions buyers ask about cost. Any correction would follow verification, not precede it.
Step 3. Align the external narrative
Questions This Section Answers
- Which cited third-party pages are relevant to fact review for Ruby?
Cited page selected for review | Citation appearances in all captured answers | Answers mentioning the company | Conflicting claims linked to this page |
|---|---|---|---|
https://fitsmallbusiness.com/best-answering-service/ | 17 | 15 | 2 |
https://upfirst.ai/blog/how-much-does-an-answering-service-cost | 15 | 13 | 2 |
https://getnextphone.com/blog/answering-service-companies | 14 | 13 | 2 |
https://zeeg.me/en/blog/post/virtual-receptionist-cost | 9 | 9 | 2 |
https://wishup.co/blog/virtual-receptionist-pricing/ | 6 | 6 | 2 |
https://withallo.com/blog/ai-call-answering-services-for-real-estate | 5 | 4 | 2 |
These pages were selected because they relate to the company in the captured answers. Their current contents still need checking before any correction request. A page linked to a conflicting claim is not necessarily its cause, and the same answer may contribute to more than one row.
Several third-party pages were cited alongside conflicting claims about Ruby, and a few of them appear repeatedly across captured answers. That makes them reasonable candidates for a closer look, but a page linked to a claim is not necessarily its cause.
We would review the current contents of the selected pages before making any request, and we would treat publisher control as uncertain. Where a page is out of date, an evidence-backed correction request may be appropriate; where it is accurate, the right outcome is a no-change decision.
Requests and responses would be logged separately so the client can see what was asked, what was confirmed and what remained unresolved.
Step 4. Optimize priority company pages
Questions This Section Answers
- Which observed Ruby website pages should receive review briefs?
Company website page | Citation appearances in all captured answers | Benchmark answers citing the page | Recommending answers citing the page |
|---|---|---|---|
https://ruby.com/ | 31 | 31 | 27 |
https://ruby.com/blog/does-your-business-need-an-answering-service/ | 15 | 15 | 11 |
https://ruby.com/plans-and-pricing/ | 9 | 9 | 1 |
https://ruby.com/virtual-receptionists-the-full-guide/what-is-a-virtual-receptionist/ | 4 | 4 | 2 |
https://ruby.com/industries/legal/ | 3 | 3 | 2 |
https://ruby.com/bilingual-answering-service/ | 2 | 2 | 2 |
https://assets.ruby.com/hubfs/Downloadable%20Assets/Other/Ruby%20Career%20Brochure%20%E2%80%93%20Receptionists.pdf | 1 | 1 | 0 |
https://ruby.com/answering-service/ | 1 | 1 | 0 |
The company's website was cited 72 times across 14 distinct page addresses; the table shows 8 pages selected for review. Zeros in the answer columns mean no matching answers were recorded. A cited page is not automatically a page that accompanied a recommendation.
Ruby's own site is cited often, with the homepage and a blog post about whether a business needs an answering service drawing the most appearances. The pricing page is cited less often and appears in very few recommending answers, which makes it a natural focus for a page brief.
We would brief priority pages using approved facts and the questions buyers actually ask, starting with the pages that already attract citations. A cited page is not automatically a page that accompanied a recommendation, so the briefs would aim to strengthen the case for endorsement rather than assume it.
Each brief would name the audience question it answers and the approved facts it may use, with legal and industry pages considered where they fit the client's priorities.
Step 5. Publish around buyer questions
Questions This Section Answers
- Which observed buyer questions support content briefs for Ruby?
Question observed in the research | Benchmark answers to this question | Company mentions | Company recommendations |
|---|---|---|---|
What is the best answering service for small business? | 6 | 6 | 6 |
What is the best answering service for real estate? | 6 | 5 | 5 |
What is the best answering service? | 6 | 5 | 5 |
What is the best phone answering service for small businesses? | 6 | 5 | 5 |
What is the phone answering service for lawyers? | 5 | 5 | 4 |
What is a good answering service? | 4 | 4 | 4 |
What is the best phone answering service? | 5 | 4 | 4 |
What is the best automated answering service for small businesses? | 3 | 3 | 3 |
These are recorded answer observations, not search volume, verified demand, or proof of missing website content.
The recorded questions are dominated by best-service comparisons for small business, real estate and legal audiences, and Ruby appears in most of the answers to them. That suggests the buyer-question territory is already familiar to the client's audience.
These are recorded answer observations, not search volume or proof that the website lacks content. Before proposing anything new, we would check existing coverage and brief only the gaps that survive that check.
Proposed briefs would answer the comparison questions directly, using approved facts and clear differentiators, so the content gives an assistant a reason to recommend rather than merely mention Ruby.
Our 90-day action plan
Questions This Section Answers
- How should the agency sequence the proposed Ruby work and judge completion?
Period | Deliverable | Completion criterion |
|---|---|---|
Days 1–30 | Baseline scorecard, scoped fact-review register and page/source shortlist | Each record has an owner, evidence requirement and review status |
Days 31–60 | Approved page briefs and justified publisher requests | Separate confirmed edits, no-change decisions, requests and responses |
Days 61–90 | Buyer-content briefs and a fresh scorecard | Record work completed separately from measured answer outcomes and comparability limits |
The first month establishes the baseline scorecard, a scoped fact-review register and a shortlist of pages and sources, each with an owner and a review status. This is groundwork: nothing is corrected or requested until the evidence is confirmed.
The second month produces approved page briefs and justified publisher requests, with confirmed edits, no-change decisions, requests and responses recorded separately. The third month adds buyer-content briefs and a fresh scorecard.
Delivered work is recorded separately from measured answer outcomes. Completing a brief or sending a request does not establish that visibility changed, and the plan does not promise a gain.
Methodology
Questions This Section Answers
- How are Ruby answer metrics and citation populations defined?
This report covers 2026-11. The exact dates when the original AI answers were collected have not been verified. The visibility rates use 367 answers that met the benchmark's inclusion rules. A company is recommended only when the answer both endorses it and uses positive wording. Top 3 and first-place counts are part of those recommendations, not extra recommendations.
An answer can mention or recommend several companies, so company counts cannot be added to find the number of distinct answers. The net sentiment score is positive minus negative mentions, divided by all company mentions; it describes answer wording, not customer satisfaction.
The wider citation analysis covers 800 captured answers and 5149 appearances of cited URLs. Citation appearances across all captured answers differ from the number of benchmark answers citing a page and the number that also recommend a company. The current contents of cited pages and disputed company claims still need independent verification.
Monthly sample coverage:
Reporting month | Answers included | AI services covered | Services |
|---|---|---|---|
Nov 2026 | 367 | 6 | ChatGPT, Copilot, Gemini, Google AI Mode, Google AI Overviews, Perplexity |
Earlier editions (July 2026, August 2026, September 2026 and October 2026) used a narrower set of questions. This edition includes all captured answers screened as relevant and establishes a broader baseline. Earlier figures remain in the archive; they are not used to claim a change in performance.
Future editions using the same screening scope can be compared against this baseline.
The report covers a single reporting month, and the exact dates when the original AI answers were collected have not been verified. Visibility rates rest on the answers that met the benchmark's inclusion rules, and a company counts as recommended only when an answer endorses it with positive wording.
An answer can mention or recommend several companies, so company counts cannot be added to find a number of distinct answers. Sentiment describes answer wording, not customer satisfaction.
The wider citation analysis covers more answers than the benchmark, and cited pages and disputed claims still need independent verification. Earlier editions used a narrower question set and are not used to claim a change in performance.
Our first three priorities
First, verify the pricing claims against current primary sources and record each as confirmed, corrected or set aside. The high-severity conflict deserves attention first, but only after the entity and date are resolved.
Second, brief the pricing page and the most-cited pages around the buyer questions the research recorded, using approved facts and a clear case for endorsement. Third, review the repeatedly cited third-party pages and decide, page by page, whether an evidence-backed request is warranted.
Each priority has a visible completion state, and none is treated as a visibility gain until a later scorecard measures it under the same screening scope.
Related research
This report supports CiteWorks Studio's examination of how AI search is recommending Virtual Receptionist Services. For more detail, you can also read Virtual Receptionist Services: AI Visibility Discovery Index.
/ Learn More
Understanding AI search visibility.
AI search experiences create answers by pulling information from many places online and summarizing it into a single response.


