Assign To on Contact Upload
complete
M
Martina Valentine
When you upload a spreadsheet of contacts, instead of only adding tags, let them be assigned to a user as well.
Log In
P
Pallavi Kothari
complete
It is now possible to also map the Contact Owner when importing a list of contacts.
P
Pallavi Kothari
Merged in a post:
Assign User When Importing Contacts
J
Jon Blacksmith ADMIN
Allowing a user to assign themselves (or others) as a user when importing contacts would save time.
D
David Santa
I just had a client ask if this was possible.
M
Matt Barbey
Shaun Clark - I'm so sorry to tag you again, but this seems like another item that is just an oversight in the storyboarding process when the import process was designed. It's is surprising that we would have to vote on this. By it's very nature, an import is often coming from another database, often a competing CRM, where they would likely already have an assigned sales rep. Having to do this through a workflow seems like an odd workaround.
M
Mark Diamond
good idea
M
Mark Diamond
good idea
M
Maher Massah
You can do that in excel file as csv file
If you search for
(CRM Assign one owner in bulk action)
And vote it will be a nice advantage
T
Tom Pacheco
you can do this with workflows. Create a workflow that is triggered with a specific tag, then add an action to assign user.
When you import the leads, it gives you the option to add tag. Put in the tag that triggers your assign user workflow.
J
Jon Blacksmith ADMIN
Tom Pacheco: Yes, this is an OK option if you only have a few clients!
I
Isaac Asher
Tom Pacheco I currently have these workflows set up but they stopped working/ I even attempted to add each import to the workflow manually, that didnt work either. Any other ideas, my client is getting restless! (Currrently waiting on hl support email to help with this issue) i need to import and assign 50,000 leads for one of my clients
T
Tom Pacheco
Isaac Asher are you adding to the workflow AFTER they are all imported?
I
Isaac Asher
Tom Pacheco I've solved the issue, it was a glitch on high level's side of things, not allowing the workflow to run properly. I fixed it the next day. Thank you for your help otherwise
Core Platform
under review