Signals
Switch on a play for each signal: a visit to your site, a new post, a new job. The play takes the next step, or asks you first.
Today
Anika B.·Head of Sales, Quanta Desk·Initial Outreach·Heads of sales, UK SaaS
Heads of sales, UK SaaS·Runningstep 3New role intro·Runningstep 1
Changed job: Head of Sales at Quanta Desk, now VP Sales at Ashgrove Data
On a job change · done · left Heads of sales, UK SaaS, entered New role intro
Sam K.·Head of Revenue, Tallyhouse·Connection Request Sent·Heads of sales, UK SaaS
Heads of sales, UK SaaS·Runningstep 2
Posted on LinkedIn
Three things we changed in how our SDRs plan the week, and the one we rolled back after a month. Monday starts with the pipeline now, not the inbox. ...more
Engage with posts · done · liked 14:32, commented 14:33
Jordan O.posted by Engage with posts
Curious which one you rolled back. In our experience the shared call list goes first.
Sam K.
It was the shared call list. Nobody owned an account after week two.
A reply as Jordan
That matches what we see. Named accounts per rep usually fix it. Did you go back to territories?
Post itDraftCancel
Jordan O.posted by hand
That matches what we see. Named accounts per rep usually fix it. Did you go back to territories?
Eva W.·VP Sales, Kinetic Forms·Initial Outreach·Heads of sales, UK SaaS
Heads of sales, UK SaaS·Runningstep 4Heads of sales, UK SaaS·Pausedstep 4Pricing follow-up·Runningstep 1
Opened the Pricing page
/pricing after the home page·came by our link·her 3rd visit this week
On a website visit · paused and asking you
Eva is in Heads of sales, UK SaaS, step 4 of 7 (the message), on hold since 11:05.
Remove from the workflowKeep goingMove to a workflow
Pick a workflowPricing follow-upMove to a workflowBack
On a website visit · done · moved to Pricing follow-up
Yesterday
Tomás F.·VP Sales, Ferro Cloud·Replied·Heads of sales, UK SaaS
Heads of sales, UK SaaS·Pausedstep 4
Opened the Pricing page
On a website visit · done · kept going in Heads of sales, UK SaaS
Lena R.·Sales Director, Tinbarrow·Replied·Heads of sales, UK SaaS
Heads of sales, UK SaaS·Pausedstep 4
Posted on LinkedIn
Engage with posts · done · liked 14:06, commented 14:07
How it works
Plays come packaged: press Set up on one, make a few choices and switch it on.
A row says what its play does and counts who qualifies now, before anything is switched on.
The whole table or one view, what it does, and Ask me or Automatic. Whoever joins the view joins the play.
A visit on a site at People, a job change or a post a workflow read: each play switched on for it acts on it once.
Each draft and question sits in Signals, under the visit, the post or the job change that raised it.
Each shows Done or Waiting for you. A pass says why, such as the weekly cap or a post over a week old.
01
Switch a play on for a table once. It answers each signal within a minute of it landing, until you stop it.
02
The links you send carry a code. On a site at People, the play pauses a visitor's journey and asks you.
At Companies, a visit shows the company only. Visitors from the EU, the EEA or the UK have to consent, and you confirm it in the site's settings.
Website visitor identificationEva W.·VP Sales, Kinetic Forms·Initial Outreach·Heads of sales, UK SaaS
Heads of sales, UK SaaS·Runningstep 4Heads of sales, UK SaaS·Pausedstep 4Pricing follow-up·Runningstep 1
Opened the Pricing page
/pricing after the home page·came by our link·her 3rd visit this week
On a website visit · paused and asking you
Eva is in Heads of sales, UK SaaS, step 4 of 7 (the message), on hold since 11:05.
Remove from the workflowKeep goingMove to a workflow
Pick a workflowPricing follow-upMove to a workflowBack
On a website visit · done · moved to Pricing follow-up
03
When a workflow reads their posts, a play likes the new ones and can comment with AI, under your brief.
Sam K.·Head of Revenue, Tallyhouse·Connection Request Sent·Heads of sales, UK SaaS
Heads of sales, UK SaaS·Runningstep 2
Posted on LinkedIn
Three things we changed in how our SDRs plan the week, and the one we rolled back after a month. Monday starts with the pipeline now, not the inbox. ...more
Engage with posts · done · liked 14:32, commented 14:33
Jordan O.posted by Engage with posts
Curious which one you rolled back. In our experience the shared call list goes first.
Sam K.
It was the shared call list. Nobody owned an account after week two.
A reply as Jordan
That matches what we see. Named accounts per rep usually fix it. Did you go back to territories?
Post itDraftCancel
Jordan O.posted by hand
That matches what we see. Named accounts per rep usually fix it. Did you go back to territories?
04
Someone in a workflow changes jobs: the play moves them to another workflow, takes them out, or asks you.
Anika B.·Head of Sales, Quanta Desk·Initial Outreach·Heads of sales, UK SaaS
Heads of sales, UK SaaS·Runningstep 3New role intro·Runningstep 1
Changed job: Head of Sales at Quanta Desk, now VP Sales at Ashgrove Data
On a job change · done · left Heads of sales, UK SaaS, entered New role intro
What it costs
Credits pay for re-reads and for the AI on a post. The AI picks the reaction unless you set one.
What a credit costsWho decides
Adds a visitor to a workflow, moves or removes on a job change, and posts the comment.
Pause and ask is the default on a visit and on a job change, in either mode.
A comment is off until you switch it on, and Ask me is the default. A like never waits.
Each signal is checked against the view, and anyone outside it is passed.
A comment draws on the post and your brief only. The AI SDR is told never to bring one up.
In B2B sales, buying signals are things people do that show interest before they say it: a visit to your pricing page, a new post, a change of job. In GetSales they come from your own outreach, your own site and the people in your tables, and a play answers the visits, the posts and the job changes.
Look at what people do with your outreach and on your site, and at what changes about them. GetSales puts each signal in one feed. On your site: visits, key pages such as pricing, forms sent and events you track. On LinkedIn: an accepted invitation, a reply, a reaction to your message, a new follower, an invitation to you, a job change and a new post a workflow reads. By email: a reply, and an open or a link click where you track them. It does not track funding, hiring, a company's tech or topics people read on other sites.
Soon, and without saying how you know: a visit to your pricing page is a reason to write today, never a line in the message. In GetSales a play answers within a minute of the signal landing, or asks you first. On a site switched to People, when someone you talk to opens a key page such as pricing, their open thread also gets a task to call them while they are still looking. That task is on by default.
A play is how you subscribe to one kind of signal on a table, and how GetSales answers it. You set it up once, and it keeps going until you stop it. On a website visit takes every visit of a person in the table, or only the pages you pick, and pauses their journey to ask you or adds them to a workflow. Engage with posts likes the new posts of people in the table once a workflow has read them, and comments with AI only if you switch the comment on. On a job change pauses the person's journeys and asks you by default, or moves them or takes them out at once. A signal no play answers still shows in the feed as Not covered, with the play to set up when there is one.
Within a minute of the signal reaching GetSales. It also runs every morning over the last two days' signals, for any it has not answered. When a signal reaches GetSales depends on its kind: a visit while the person is still on your site, a job change once a day from your sender profiles' networks or when Keep data fresh re-reads the profile, a post when one of your workflows reads it. What a play sends then goes out on the sender profile's own schedule, within its limits.
Only when you switch the comment on and choose Automatic. In Ask me, the default, the comment waits in Signals under the post, and you post it, edit it or skip it. The like goes at once either way, and the play acts on each person at most twice a week by default, a number you set.
Each link to your site that you send carries a code, and a visit through it names the company you wrote to, or the person on a site switched to People. The setup, the levels and what to disclose are on Website visitor identification.
Part of it is. A visit, an open and a reply are first-party: they come from your own links, site and messages. Posts and job changes are news about people already in your tables. None of it is bought topic intent, and GetSales names a person only when you already have them. If you buy topic intent, keep that vendor beside it.
A visit spends none, and neither does a job change a play acts on or a like with the reaction you pick. On a post, the AI's comment spends credits, and so does the reaction when the AI picks it, which is the default. A profile re-read by Keep data fresh spends credits too. A daily ceiling you can set caps what a play spends, and what a credit costs is on the pricing page.
A table with the people you write to and the plays you want switched on. Engage with posts needs a sender profile with its LinkedIn account connected, and so do the job changes seen through your network. For site visits, also the snippet on your site with its consent settings confirmed. Sign up free: Playtables stay free with your own API keys, and LinkedIn and email come with a 7-day trial.
On watch
Switch a play on once. It answers visits, posts and job changes as they land.
Each one answers within a minute, until you stop it.
Write while it counts.
Press "Start a call" below to talk.
