Publishing contacts to opt-in users

1. A method for reducing backlog at a call center, the method comprising:

receiving a request for an agent of a contact center from a device associated with a contact;

determining a context for the request;

publishing, based on the context, the request to a portal service while restricting agents at the contact center from servicing the request;

monitoring a time that the request is published to the portal service;

receiving an interrupt from a device associated with an opt-in user, wherein the interrupt indicates that the opt-in user would like to handle the published request;

performing if the interrupt is received:

coupling, communicably, the device associated with the opt-in user to the device associated with the contact after; and

performing if the time that the request is published to the portal service surpasses a threshold and an interrupt from a device associated with an opt-in user is not received:

removing the request from being published to the portal service; and

allowing agents at the contact center to service the request.

2. The method of claim 1 , wherein performing if the interrupt is received further comprises:

reporting, to the contact center, an outcome of an interaction between the contact and the opt-in user.

3. The method of claim 1 , wherein publishing, based on the context, the request to a portal service while restricting agents at the contact center from servicing the request comprises publishing, based on the context, the request to a portal service while restricting agents at the contact center from servicing the request only if a backlog of the call center surpasses a threshold.

4. The method of claim 1 , wherein determining a context for the request further comprises determining a context for the request based on an identity of the contact.

5. The method of claim 1 , wherein determining a context for the request further comprises determining a context for the request based on a type of request.

6. The method of claim 1 , wherein determining a context for the request further comprises determining a context for the request based on an identification of the contact's actions before the contact issued the request.

7. The method of claim 6 , wherein determining a context for the request based on an identification of the contact's actions before the contact issued the request comprises:

determining that the request is from a contact on a web site;

determining a browsing history of the contact while the contact was on the web site; and

determining the context based on the browsing history of the contact.

8. The method of claim 6 , wherein determining a context for the request based on an identification of the contact's actions before the contact issued the request comprises:

determining that the request is from a contact on a phone system;

presenting the contact with choices regarding the request;

receiving a selection from the contact based on the choices presented to the contact; and

determining the context based on the selection based on the choices presented to the contact received from the contact.

9. The method of claim 1 further comprising:

receiving, from the device associated with the opt-in user, settings for a filter that filters published requests based on the contexts of the published requests; and

sending a notification to the device associated with the opt-in user that a request meeting the filter settings is available.

10. The method of claim 1 further comprising:

receiving, from the device associated with the opt-in user, settings for a filter that filters published requests based on the contexts of the published requests; and

ordering the published requests based on the filter settings.

11. Computer-readable hardware with a program for reducing backlog at a call center stored thereon, wherein the computer program instructs a processor to perform:

receiving a request for an agent of a contact center from a device associated with a contact;

determining a context for the request;

publishing, based on the context, the request to a portal service while restricting agents at the contact center from servicing the request;

monitoring a time that the request is published to the portal service;

receiving an interrupt from a device associated with an opt-in user, wherein the interrupt indicates that the opt-in user would like to handle the published request;

performing if the interrupt is received:

coupling, communicably, the device associated with the opt-in user to the device associated with the contact after; and

performing if the time that the request is published to the portal service surpasses a threshold and an interrupt from a device associated with an opt-in user is not received:

removing the request from being published to the portal service; and

allowing agents at the contact center to service the request.

12. The computer-readable hardware of claim 11 , wherein performing if the interrupt is received further comprises:

reporting, to the contact center, an outcome of an interaction between the contact and the opt-in user.

13. The computer-readable hardware of claim 11 , wherein publishing, based on the context, the request to a portal service without publishing the request to a contact center comprises publishing, based on the context, the request to a portal service without publishing the request to a contact center only if a backlog of the call center surpasses a threshold.

14. The computer-readable hardware of claim 11 , wherein determining a context for the request further comprises determining a context for the request based on an identity of the contact.

15. The computer-readable hardware of claim 11 , wherein determining a context for the request further comprises determining a context for the request based on a type of request.

16. The computer-readable hardware of claim 11 , wherein determining a context for the request further comprises determining a context for the request based on an identification of the contact's actions before the contact issued the request.

17. The computer-readable hardware of claim 16 , wherein determining a context for the request based on an identification of the contact's actions before the contact issued the request comprises:

determining that the request is from a contact on a web site;

determining a browsing history of the contact while the contact was on the web site; and

determining the context based on the browsing history of the contact.

18. The computer-readable hardware of claim 16 , wherein determining a context for the request based on an identification of the contact's actions before the contact issued the request comprises:

determining that the request is from a contact on a phone system;

presenting the contact with choices regarding the request;

receiving a selection from the contact based on the choices presented to the contact; and

determining the context based on the selection based on the choices presented to the contact received from the contact.

19. The computer-readable hardware of claim 11 , wherein the program further instructs the processor to perform:

receiving, from the device associated with the opt-in user, settings for a filter that filters published requests based on the contexts of the published requests; and

sending a notification to the device associated with the opt-in user that a request meeting the filter settings is available.

20. The computer-readable hardware of claim 11 , wherein the program further instructs the processor to perform:

receiving, from the device associated with the opt-in user, settings for a filter that filters published requests based on the contexts of the published requests; and

ordering the published requests based on the filter settings.