juni 9, 2021
Båda delar kan fylla sitt tydliga syfte i olika lägen av säljcykeln. Det är en anledning till varför man skiljer på Leads och Prospekts. Ett lead är ett lead så länge det är okvalificerat. Så snart leadet kvalificerats av en säljare eller av data, så kan leadet konverteras till att bli ett Prospekt. Lead och Prospekt är alltså en form av kategorisering på dina kontaktpersoner, detta så att det är enklare att prioritera dina arbetsinsatser.
Jag letar efter ett ekonomisystem som passar mitt företag med 2 anställda. Jag hittar ett verktyg som verkar passande men jag behöver veta mer för att kunna avgöra om verktyget är rätt för min typ av bolag. Mina kontaktuppgifter landar nu som ett Lead hos företaget. Varför? Jo, än så länge vet de inte om deras lösning passar mig, mitt företag eller mina behov. Därför är jag okvalificerad. En stund senare ringer en säljare upp mig. Vi pratar och jag berättar om vad jag är ute efter, turligt nog låter det som att verktyget de säljer kommer att passa mig alldeles utmärkt. Jippie! Efter vårt samtal kvalificerar säljaren mig och kategoriserar om mig från att vara ett Lead, till att bli ett hett Prospekt.
Genom att kategorisera våra kontakter underlättar vi för säljare, säljchefer eller andra anställda att snabbt veta hur de ska prioritera eller agera i relationen. Ett Prospekt som är kvalificerat har högre sannolikhet att köpa än ett kallt Lead. I alla fall till dess att Leadet har kvalificerats. Högst sannolikhet till köp prioriteras först!
Vi lovar att du kommer tacka dig själv i framtiden om du slipper ha ett system fullt av okvalificerade kontakter.
Det händer givetvis att leads inte är kvalificerade eller en perfect match. I de fallen är det extra skönt om du redan från början sett till att hålla dina datakällor separerade när det kommer till leads och prospekt. Vi lovar att du kommer tacka dig själv i framtiden om du slipper ha ett system fullt av okvalificerade kontakter. För allra bäst hantering av kundregister, kontaktpersoner, leads och prospekts behöver du såklart ett CRM-system. Testa själv! Vi bjuder på 14 dagar gratis testperiod av Cirrus CRM om du signar upp dig 👉 här 👈
We use cookies to enhance your browsing experience and analyze our traffic. Please choose which cookies you want to accept.
Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.
No cookies or scripts detected in this category yet.
Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in.
| Name | Provider | Purpose | Maximum Storage Duration | Type |
|---|---|---|---|---|
| cirruscrm_io_cookie | Cirruscrm | Third-party service | Unknown | Third party |
| consent_cookiebot_com_cookie | Cookiebot | Third-party service | Unknown | Third party |
| intercom-id | Intercom | Set by Intercom | Varies | Http |
| intercom-session | Intercom | Set by Intercom | Varies | Http |
| NID | Google Maps | Registers a unique ID that identifies a returning user's device. The ID is used for targeted ads. | 6 months | Http |
| pll_language | Polylang | — | 2026-11-24 07:34:00 | Http |
Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.
| Name | Provider | Purpose | Maximum Storage Duration | Type |
|---|---|---|---|---|
| _ga | Google Analytics | Registers a unique ID that is used to generate statistical data on how the visitor uses the website. | 2 years | Http |
| _ga_# | Google Analytics | Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit. | 2 years | Http |
| _gat | Google Analytics | Used by Google Analytics to throttle request rate. | 1 day | Http |
| _gid | Google Analytics | Registers a unique ID that is used to generate statistical data on how the visitor uses the website. | 1 day | Http |
| _gtm | Google Tag Manager | Set by Google Tag Manager | Varies | Http |
| _hjAbsoluteSessionInProgress | Hotjar | This cookie is used to count how many times a website has been visited by different visitors. | 1 day | Http |
| _hjid | Hotjar | Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. | 1 year | Http |
| _hjIncludedInPageviewSample | Hotjar | Used to detect whether the user navigation and interactions are included in the website's data analytics. | 1 day | Http |
| _hjIncludedInSessionSample_# | Hotjar | Determines if the user's navigation should be registered in a certain statistical place holder. | 1 day | Http |
| _hjSession_# | Hotjar | Collects statistics on the visitor's visits to the website, such as the number of visits, average time spent on the website and what pages have been read. | 1 day | Http |
| _hjSessionUser_# | Hotjar | Collects statistics on the visitor's visits to the website, such as the number of visits, average time spent on the website and what pages have been read. | 1 year | Http |
| Google Analytics 4 | Google Analytics 4 | Script blocking | — | Script |
Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user.
| Name | Provider | Purpose | Maximum Storage Duration | Type |
|---|---|---|---|---|
| _fbp | Facebook Pixel | Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers. | 3 months | Http |
| fr | Facebook Pixel | Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers. | 3 months | Http |
| _gcl_au | Google AdSense | Used by Google AdSense for experimenting with advertisement efficiency across websites using their services. | 3 months | Http |
| _mcid | Mailchimp | Set by Mailchimp | Varies | Http |
| _twitter_sess | Twitter/X Pixel | Used by Twitter to track user sessions and authentication status. | Session | Http |
| personalization_id | Twitter/X Pixel | Used by Twitter for tracking and personalized advertising. | 2 years | Http |
| bcookie | LinkedIn Insight Tag | Used by the social networking service, LinkedIn, for tracking the use of embedded services. | 1 year | Http |
| li_fat_id | LinkedIn Insight Tag | Used by the social networking service, LinkedIn, for tracking the use of embedded services. | 30 days | Http |
| li_sugr | LinkedIn Insight Tag | Collects data on user behaviour and interaction in order to optimize the website and make advertisement on the website more relevant. | 3 months | Http |
| CONSENT | YouTube | Used to detect if the visitor has accepted the marketing category in the cookie banner. | 2 years | Http |
| VISITOR_INFO1_LIVE | YouTube | Tries to estimate users' bandwidth on pages with integrated YouTube videos. | 180 days | Http |
| YSC | YouTube | Registers a unique ID to keep statistics of what videos from YouTube the user has seen. | Session | Http |
| yt-remote-connected-devices | YouTube | Stores the user's video player preferences using embedded YouTube video. | Persistent | Http |
| yt-remote-device-id | YouTube | Stores the user's video player preferences using embedded YouTube video. | Persistent | Http |
| IDE | Google Ads | Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads. | 1 year | Http |
| test_cookie | Google Ads | Used to check if the user's browser supports cookies. | 1 day | Http |
| vuid | Vimeo | Collects data on the user's visits to the website, such as which pages have been read. | 2 years | Http |
| www_googletagmanager_com_iframe | Googletagmanager | Embedded content | Varies | Iframe |
| Script blocking | — | Script | ||
| Script blocking | — | Script | ||
| Twitter/X | Twitter/X | Script blocking | — | Script |