[Solved] Alter data on incoming DID Calls

[davesdatasystems]

I do not know if this is possible. I am going to try to use a sample here to tell you what i was to try.

Call comes in from a inbound DID. The call goes to a agent. There is no lead for this caller.

I want to know if you can enter and save information and take notes on a inound DID caller that is not a lead already in the dialer.

[mflorell]

If the call goes to an agent logged into Vicidial, then a new lead would be created for the caller, and you could put information into that lead.

[davesdatasystems]

I guess i might a missed a important part Matt.

I know the call go into the Default inbound list, but what if the person wants to enter information into the agent display and wants that info to be saved for the next time that same number calls in a second, third or forth time or more over a long period of time, how would that information be saved so that the data always shows up. The data that the agent entered on the first call.

I did a few test with agent altar data on, it did not seem to save information in the way i wanted it to.

[davesdatasystems]

I just opened my default inbound list and i see the edits in the inbound list, i guess i am asking if there is a way to force a phone number calling in from the inbound DID to open the edited version of the list on the agent display screen when someone is calling in.

[mflorell]

Yes, that's what the CIDLOOKUP options in the In-Group Handle Method setting for a DID is for.

[davesdatasystems]

Thanks Matt, i will try that out.

Edit: Worked just like you said, thanks. I would of never found that setting without your help.

[mflorell]

Thanks for the postback!

[williamconley]

For future reference: (DID Setting)

In-Group Call Handle Method -If IN_GROUP is selected as the DID Route, then this is the call handling method used for these calls. CID will add a new lead record with every call using the CallerID as the phone number, CIDLOOKUP will attempt to lookup the phone number by the CallerID in the entire system, CIDLOOKUPRL will attempt to lookup the phone number by the CallerID in only one specified list, CIDLOOKUPRC will attempt to lookup the phone number by the CallerID in all of the lists that belong to the specified campaign, CLOSER is specified for Closer calls, ANI will add a new lead record with every call using the ANI as the phone number, ANILOOKUP will attempt to lookup the phone number by the ANI in the entire system, ANILOOKUPRL will attempt to lookup the phone number by the ANI in only one specified list, XDIGITID will prompt the caller for an X digit code before the call will be put into the queue, VIDPROMPT will prompt the caller for their ID number and will create a new lead record with the CallerID as the phone number and the ID as the Vendor ID, VIDPROMPTLOOKUP will attempt to lookup the ID in the entire system, VIDPROMPTLOOKUPRL will attempt to lookup the vendor ID by the ID in only one specified list, VIDPROMPTLOOKUPRC will attempt to lookup the vendor ID by the ID in all of the lists that belong to the specified campaign. Default is CID. If a CIDLOOKUP method is used with ALT, it will search the alt_phone field for the phone number if no matches are found for the main phone number. If a CIDLOOKUP method is used with ADDR3, it will search the address3 field for the phone number if no matches are found for the main phone number and optionally the alt_phone field.

[davesdatasystems]

Thanks William, that little setting has a lot going on. I guess that is why it is called the call HANDLE method. I never really needed it, so it was always something i left "as is"

[williamconley]

It's a two-edged blade.

On the one hand, you should always set it to check the entire system to find your match, then you should never have two of the same lead in your system (I mean, why would you want two of the same lead in your system? That's just gonna cause confusion, right? LOL)

On the other hand, if you track sales by the lead status, and a lead calls back in and talks to a rep ... that rep is not likely to set "SALE" unless they personally made a sale. So that lead's status could change and screw up your reporting. So there are issues ...