Answers, without opening a ticket

Any Excel or CSV export you already have - Sales Navigator lists, event attendees, conference lists, your own research. Uploads are cumulative: a second upload of 500 records adds to the existing 1,000 rather than replacing them.

They are detected on LinkedIn URL, email address, or name plus company, then merged or updated instead of duplicated. Every import keeps its own history so you can always see where a record came from.

The platform itself is built. Setup is your company profile, your Ideal Customer Profile and your outreach owners - a short onboarding, then your first import and first scored queue.

No. The platform ships with a human-assisted action queue: Dizenly decides who to contact and drafts what to say, and your team performs the LinkedIn action from their own account. If official API access is granted later, the connector replaces those manual steps and nothing else in the platform changes.

It is tagged Neutral, which pauses the sequence and returns the prospect to the pool for a later follow-up cycle. The system never sends the next message before a reply has been classified.

Exactly the number you set. The daily limit is configurable globally and per owner. Unused capacity rolls into the next cycle and prospects keep their rank rather than moving to the back of the queue.

No. Dizenly sits before the CRM in the funnel - it decides who to contact, in what order, and drafts the first message. Qualified conversations still land in your CRM the way they do today; a direct export or sync is on the near-term roadmap.

Criteria-based allocation routes a prospect to the rep who already owns that territory, industry or account before round-robin or capacity rules ever apply, so existing ownership rules are never overridden.

Pause their outreach owner profile in Settings and their share of the queue redistributes to the rest of the team on the next allocation cycle - nothing sits untouched waiting for them to come back.

No. Candidate scoring runs against the live requisition's requirements - skills, seniority, availability. Hiring-manager and company scoring runs against a separate business-development ICP. They are two independent configurations, not one blended score.

Candidate records are stored and scored the same way any prospect record is - with a full audit trail of what was captured and when. Your existing candidate-data and consent obligations under applicable recruitment and data-protection rules still apply; Dizenly does not change what you are permitted to hold or contact.

Yes. Criteria-based allocation can be configured per requisition, so a cross-functional search pulls candidates sourced by more than one specialist desk into a single ranked pipeline.